Searched refs:backends (Results 1 – 21 of 21) sorted by relevance
| /Linux-v5.15/drivers/block/zram/ |
| D | zcomp.c | 17 static const char * const backends[] = { variable
68 i = sysfs_match_string(backends, comp); in zcomp_available_algorithm()
89 for (i = 0; i < ARRAY_SIZE(backends); i++) { in zcomp_available_show()
90 if (!strcmp(comp, backends[i])) { in zcomp_available_show()
93 "[%s] ", backends[i]); in zcomp_available_show()
96 "%s ", backends[i]); in zcomp_available_show()
|
| /Linux-v5.15/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.15/drivers/gpu/drm/i915/gem/selftests/ |
| D | huge_pages.c | 1283 } backends[] = { in igt_ppgtt_smoke_huge() local
1296 for (i = 0; i < ARRAY_SIZE(backends); ++i) { in igt_ppgtt_smoke_huge()
1297 u32 min = backends[i].min; in igt_ppgtt_smoke_huge()
1298 u32 max = backends[i].max; in igt_ppgtt_smoke_huge()
1303 obj = backends[i].fn(i915, size, 0); in igt_ppgtt_smoke_huge()
1367 } backends[] = { in igt_ppgtt_sanity_check() local
1399 for (i = 0; i < ARRAY_SIZE(backends); ++i) { in igt_ppgtt_sanity_check()
1405 obj = backends[i].fn(i915, size, backends[i].flags); in igt_ppgtt_sanity_check()
|
| /Linux-v5.15/fs/ecryptfs/ |
| D | Kconfig | 23 backends, like OpenSSL.
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-driver-xen-blkback | 45 that this option only takes effect on newly created backends.
|
| D | pstore | 44 backends are available, the preferred backend may be
|
| /Linux-v5.15/drivers/vhost/ |
| D | Kconfig | 72 guest virtio devices with the vDPA-based backends.
|
| /Linux-v5.15/samples/bpf/ |
| D | README.rst | 60 By default llvm will build all non-experimental backends including bpf.
|
| /Linux-v5.15/drivers/virtio/ |
| D | Kconfig | 37 virtio backends. Most QEMU based VMMs should support these devices
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | llvm.rst | 38 A single Clang compiler binary will typically contain all supported backends,
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | console.rst | 35 examined. This shows the console backends currently registered by the
|
| /Linux-v5.15/drivers/platform/x86/dell/ |
| D | Kconfig | 99 # backends are selected. The "depends" line prevents a configuration
|
| /Linux-v5.15/Documentation/filesystems/caching/ |
| D | operations.rst | 30 This facility is available to and expected to be used by the cache backends,
|
| D | fscache.rst | 13 FS-Cache mediates between cache backends (such as CacheFS) and network
254 |Lookups |n=N |Number of lookup calls made on cache backends |
|
| D | object.rst | 32 the fscache_object struct. The cache backends allocate these upon request, and
|
| /Linux-v5.15/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.15/Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 55 * Even when using the DRM scheduler the backends will handle
|
| /Linux-v5.15/Documentation/staging/ |
| D | remoteproc.rst | 29 existing virtio drivers with remote processor backends at a minimal development
|
| /Linux-v5.15/Documentation/admin-guide/sysctl/ |
| D | net.rst | 95 JIT backends. Enabling hardening trades off performance, but can
|
| /Linux-v5.15/Documentation/power/ |
| D | swsusp.rst | 185 encryption) and arbitrary backends for writing the image (eg to swap
|
