Searched refs:backends (Results 1 – 14 of 14) sorted by relevance
| /linux-4.4.14/drivers/block/zram/ |
| D | zcomp.c | 46 static struct zcomp_backend *backends[] = { variable
57 while (backends[i]) { in find_backend()
58 if (sysfs_streq(compress, backends[i]->name)) in find_backend()
62 return backends[i]; in find_backend()
276 while (backends[i]) { in zcomp_available_show()
277 if (!strcmp(comp, backends[i]->name)) in zcomp_available_show()
279 "[%s] ", backends[i]->name); in zcomp_available_show()
282 "%s ", backends[i]->name); in zcomp_available_show()
|
| /linux-4.4.14/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
180 * For backends simulating hardware registers, buffers are not helpful because
|
| /linux-4.4.14/fs/ecryptfs/ |
| D | Kconfig | 22 backends, like OpenSSL.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | pstore | 44 backends are available, the preferred backend may be
|
| /linux-4.4.14/drivers/virtio/ |
| D | Kconfig | 17 virtio backends. Most QEMU based VMMs should support these devices
|
| /linux-4.4.14/Documentation/mic/ |
| D | mic_overview.txt | 36 virtio backends are situated on the host rather than the card given better
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 31 examined. This shows the console backends currently registered by the
|
| /linux-4.4.14/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-4.4.14/Documentation/vm/ |
| D | cleancache.txt | 234 is not an architectural restriction, but no backends currently
237 hook to get best performance for some backends.
|
| D | frontswap.txt | 7 all other supporting code -- the "backends" -- is implemented as drivers.
206 backends because it grants completely dynamic discretion to the
|
| /linux-4.4.14/Documentation/ |
| D | remoteproc.txt | 26 existing virtio drivers with remote processor backends at a minimal development
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp.txt | 156 encryption) and arbitrary backends for writing the image (eg to swap
|