Home
last modified time | relevance | path

Searched refs:backends (Results 1 – 20 of 20) sorted by relevance

/Linux-v5.10/drivers/block/zram/
Dzcomp.c17 static const char * const backends[] = { variable
66 i = sysfs_match_string(backends, comp); in zcomp_available_algorithm()
87 for (i = 0; i < ARRAY_SIZE(backends); i++) { in zcomp_available_show()
88 if (!strcmp(comp, backends[i])) { in zcomp_available_show()
91 "[%s] ", backends[i]); in zcomp_available_show()
94 "%s ", backends[i]); in zcomp_available_show()
/Linux-v5.10/Documentation/i2c/
Dslave-interface.rst34 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.10/drivers/gpu/drm/i915/gem/selftests/
Dhuge_pages.c1252 } backends[] = { in igt_ppgtt_smoke_huge() local
1265 for (i = 0; i < ARRAY_SIZE(backends); ++i) { in igt_ppgtt_smoke_huge()
1266 u32 min = backends[i].min; in igt_ppgtt_smoke_huge()
1267 u32 max = backends[i].max; in igt_ppgtt_smoke_huge()
1272 obj = backends[i].fn(i915, size, 0); in igt_ppgtt_smoke_huge()
1334 } backends[] = { in igt_ppgtt_sanity_check() local
1365 for (i = 0; i < ARRAY_SIZE(backends); ++i) { in igt_ppgtt_sanity_check()
1371 obj = backends[i].fn(i915, size, backends[i].flags); in igt_ppgtt_sanity_check()
/Linux-v5.10/fs/ecryptfs/
DKconfig23 backends, like OpenSSL.
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-driver-xen-blkback45 that this option only takes effect on newly created backends.
Dpstore44 backends are available, the preferred backend may be
/Linux-v5.10/drivers/vhost/
DKconfig72 guest virtio devices with the vDPA-based backends.
/Linux-v5.10/Documentation/kbuild/
Dllvm.rst38 A single Clang compiler binary will typically contain all supported backends,
/Linux-v5.10/samples/bpf/
DREADME.rst60 By default llvm will build all non-experimental backends including bpf.
/Linux-v5.10/drivers/virtio/
DKconfig28 virtio backends. Most QEMU based VMMs should support these devices
/Linux-v5.10/Documentation/driver-api/
Dconsole.rst35 examined. This shows the console backends currently registered by the
/Linux-v5.10/Documentation/filesystems/caching/
Doperations.rst30 This facility is available to and expected to be used by the cache backends,
Dfscache.rst13 FS-Cache mediates between cache backends (such as CacheFS) and network
254 |Lookups |n=N |Number of lookup calls made on cache backends |
Dobject.rst32 the fscache_object struct. The cache backends allocate these upon request, and
/Linux-v5.10/Documentation/vm/
Dcleancache.rst253 is not an architectural restriction, but no backends currently
256 hook to get best performance for some backends.
Dfrontswap.rst13 all other supporting code -- the "backends" -- is implemented as drivers.
221 backends because it grants completely dynamic discretion to the
/Linux-v5.10/Documentation/staging/
Dremoteproc.rst29 existing virtio drivers with remote processor backends at a minimal development
/Linux-v5.10/Documentation/admin-guide/sysctl/
Dnet.rst95 JIT backends. Enabling hardening trades off performance, but can
/Linux-v5.10/Documentation/power/
Dswsusp.rst185 encryption) and arbitrary backends for writing the image (eg to swap
/Linux-v5.10/drivers/platform/x86/
DKconfig323 # backends are selected. The "depends" line prevents a configuration