Searched refs:backends (Results 1 – 17 of 17) sorted by relevance
| /Linux-v4.19/drivers/block/zram/ |
| D | zcomp.c | 21 static const char * const backends[] = { variable
73 i = __sysfs_match_string(backends, -1, comp); in zcomp_available_algorithm()
94 for (; backends[i]; i++) { in zcomp_available_show()
95 if (!strcmp(comp, backends[i])) { in zcomp_available_show()
98 "[%s] ", backends[i]); in zcomp_available_show()
101 "%s ", backends[i]); in zcomp_available_show()
|
| /Linux-v4.19/Documentation/mic/ |
| D | mic_overview.txt | 20 backends or devices on the host which are used to probe virtio drivers
24 space backends on the host via a device page. Ring 3 apps on the host
45 virtio backends are situated on the host rather than the card given better
|
| /Linux-v4.19/Documentation/i2c/ |
| D | slave-interface | 33 I2C slave backends behave like standard I2C clients. So, you can instantiate
35 is that i2c slave backends have their own address space. So, you have to add
51 drivers and writing backends will be given.
121 Software backends
185 * For backends simulating hardware registers, buffers are largely not helpful
|
| /Linux-v4.19/fs/ecryptfs/ |
| D | Kconfig | 22 backends, like OpenSSL.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | pstore | 44 backends are available, the preferred backend may be
|
| /Linux-v4.19/drivers/virtio/ |
| D | Kconfig | 21 virtio backends. Most QEMU based VMMs should support these devices
|
| /Linux-v4.19/samples/bpf/ |
| D | README.rst | 48 By default llvm will build all non-experimental backends including bpf.
|
| /Linux-v4.19/Documentation/console/ |
| D | console.txt | 32 examined. This shows the console backends currently registered by the
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/ |
| D | remoteproc.txt | 29 existing virtio drivers with remote processor backends at a minimal development
|
| /Linux-v4.19/Documentation/sysctl/ |
| D | net.txt | 76 JIT backends. Enabling hardening trades off performance, but can
|
| /Linux-v4.19/Documentation/power/ |
| D | swsusp.txt | 164 encryption) and arbitrary backends for writing the image (eg to swap
|
| /Linux-v4.19/drivers/platform/x86/ |
| D | Kconfig | 110 # backends are selected. The "depends" line prevents a configuration
|
