Searched refs:backends (Results 1 – 17 of 17) sorted by relevance
| /Linux-v5.4/drivers/block/zram/ |
| D | zcomp.c | 17 static const char * const backends[] = { variable
70 i = __sysfs_match_string(backends, -1, comp); in zcomp_available_algorithm()
91 for (; backends[i]; i++) { in zcomp_available_show()
92 if (!strcmp(comp, backends[i])) { in zcomp_available_show()
95 "[%s] ", backends[i]); in zcomp_available_show()
98 "%s ", backends[i]); in zcomp_available_show()
|
| /Linux-v5.4/Documentation/mic/ |
| D | mic_overview.rst | 24 backends or devices on the host which are used to probe virtio drivers
28 space backends on the host via a device page. Ring 3 apps on the host
49 virtio backends are situated on the host rather than the card given better
|
| /Linux-v5.4/Documentation/i2c/ |
| D | slave-interface.rst | 34 I2C slave backends behave like standard I2C clients. So, you can instantiate
36 is that i2c slave backends have their own address space. So, you have to add
52 drivers and writing backends will be given.
127 Software backends
191 * For backends simulating hardware registers, buffers are largely not helpful
|
| /Linux-v5.4/fs/ecryptfs/ |
| D | Kconfig | 23 backends, like OpenSSL.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | pstore | 44 backends are available, the preferred backend may be
|
| /Linux-v5.4/samples/bpf/ |
| D | README.rst | 48 By default llvm will build all non-experimental backends including bpf.
|
| /Linux-v5.4/drivers/virtio/ |
| D | Kconfig | 22 virtio backends. Most QEMU based VMMs should support these devices
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | console.rst | 35 examined. This shows the console backends currently registered by the
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | operations.txt | 29 This facility is available to and expected to be be used by the cache backends,
|
| D | fscache.txt | 12 FS-Cache mediates between cache backends (such as CacheFS) and network
234 Lookups n=N Number of lookup calls made on cache backends
|
| D | object.txt | 31 the fscache_object struct. The cache backends allocate these upon request, and
|
| /Linux-v5.4/Documentation/vm/ |
| D | cleancache.rst | 253 is not an architectural restriction, but no backends currently
256 hook to get best performance for some backends.
|
| D | frontswap.rst | 13 all other supporting code -- the "backends" -- is implemented as drivers.
221 backends because it grants completely dynamic discretion to the
|
| /Linux-v5.4/Documentation/ |
| D | remoteproc.txt | 29 existing virtio drivers with remote processor backends at a minimal development
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | net.rst | 94 JIT backends. Enabling hardening trades off performance, but can
|
| /Linux-v5.4/Documentation/power/ |
| D | swsusp.rst | 184 encryption) and arbitrary backends for writing the image (eg to swap
|
| /Linux-v5.4/drivers/platform/x86/ |
| D | Kconfig | 130 # backends are selected. The "depends" line prevents a configuration
|
