/linux-4.1.27/Documentation/ABI/stable/ |
D | sysfs-bus-xen-backend | 1 What: /sys/bus/xen-backend/devices/*/devtype 9 What: /sys/bus/xen-backend/devices/*/nodename 15 backend device. 17 What: /sys/bus/xen-backend/devices/vbd-*/physical_device 23 physical device providing the storage for this backend 26 What: /sys/bus/xen-backend/devices/vbd-*/mode 34 What: /sys/bus/xen-backend/devices/vbd-*/statistics/f_req 41 What: /sys/bus/xen-backend/devices/vbd-*/statistics/oo_req 46 Number of requests delayed because the backend was too 49 What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_req [all …]
|
/linux-4.1.27/tools/perf/Documentation/ |
D | asciidoc.conf | 21 ifdef::backend-docbook[] 27 endif::backend-docbook[] 29 ifdef::backend-docbook[] 67 endif::backend-docbook[] 70 ifdef::backend-docbook[] 85 endif::backend-docbook[] 88 ifdef::backend-xhtml11[] 91 endif::backend-xhtml11[]
|
/linux-4.1.27/drivers/block/zram/ |
D | zcomp.c | 68 comp->backend->destroy(zstrm->private); in zcomp_strm_free() 83 zstrm->private = comp->backend->create(); in zcomp_strm_alloc() 307 return comp->backend->compress(src, zstrm->buffer, dst_len, in zcomp_compress() 314 return comp->backend->decompress(src, src_len, dst); in zcomp_decompress() 334 struct zcomp_backend *backend; in zcomp_create() local 337 backend = find_backend(compress); in zcomp_create() 338 if (!backend) in zcomp_create() 345 comp->backend = backend; in zcomp_create()
|
D | zcomp.h | 45 struct zcomp_backend *backend; member
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-driver-xen-blkfront | 7 with the backend for indirect descriptors. The default value 9 memory usage. The backend picks the minimum of the frontend 10 and its default backend value.
|
D | pstore | 43 Pstore only supports one backend at a time. If multiple 44 backends are available, the preferred backend may be 45 set by passing the pstore.backend= argument to the kernel at
|
D | sysfs-driver-xen-blkback | 7 backend buffer.
|
D | sysfs-bus-event_source-devices-events | 7 /sys/devices/cpu/events/stalled-cycles-backend
|
D | sysfs-block-zram | 65 number of backend's zcomp_strm compression streams (number of
|
/linux-4.1.27/Documentation/i2c/ |
D | slave-interface | 7 Besides this HW requirement, one also needs a software backend providing the 11 retrieve/provide information as needed. The software backend driver and the I2C 14 example. The backend could also use e.g. a character device, be in-kernel 26 Note: Technically, there is also the I2C core between the backend and the 39 Each backend should come with separate documentation to describe its specific 49 The bus driver sends an event to the backend using the following function: 57 is the return value from the backend. Mandatory events must be provided by the 58 bus drivers and must be checked for by backend drivers. 74 'val': backend returns first byte to be sent 92 'val': backend returns next byte to be sent [all …]
|
D | slave-eeprom-backend | 1 Linux I2C slave eeprom backend 6 This is a proof-of-concept backend which acts like an EEPROM on the connected
|
/linux-4.1.27/Documentation/vm/ |
D | frontswap.txt | 41 If a backend chooses, frontswap can be configured as a "writethrough 44 in order to allow the backend to arbitrarily "reclaim" space used to 61 A backend implementation may provide additional metrics. 106 Specifically, the Xen Transcendent Memory backend allows otherwise 125 swap device. If CONFIG_FRONTSWAP is enabled but no frontswap "backend" 128 AND a frontswap backend registers AND the backend fails every "store" 135 As for space, if CONFIG_FRONTSWAP is enabled AND a frontswap backend 148 backend, such as zcache, must implement policies to carefully (but 154 Let's assume that a frontswap "backend" has registered during 156 frontswap backend has access to some "memory" that is not directly [all …]
|
D | cleancache.txt | 28 A cleancache "backend" that provides transcendent memory registers itself 94 A backend implementation may provide additional metrics. 126 Specifically, the Xen Transcendent Memory backend allows otherwise 148 compare-to-NULL if config'ed on but no backend claims the ops 150 backend claims the ops functions but a filesystem doesn't enable 176 on both the frontend and backend and also allows the backend to 194 The invalidate is done by the cleancache backend implementation. 268 backend may have less value for KVM. This remains to be tested,
|
/linux-4.1.27/drivers/xen/xenbus/ |
D | xenbus_probe_frontend.c | 406 char *backend, *frontend; in xenbus_check_frontend() local 421 backend = xenbus_read(XBT_NIL, frontend, "backend", NULL); in xenbus_check_frontend() 422 if (!backend || IS_ERR(backend)) in xenbus_check_frontend() 424 err = xenbus_scanf(XBT_NIL, backend, "state", "%i", &be_state); in xenbus_check_frontend() 426 xenbus_reset_frontend(frontend, backend, be_state); in xenbus_check_frontend() 427 kfree(backend); in xenbus_check_frontend()
|
/linux-4.1.27/drivers/firmware/efi/ |
D | Kconfig | 22 tristate "Register efivars backend for pstore" 26 Say Y here to enable use efivars as a backend to pstore. This 31 bool "Disable using efivars as a pstore backend by default" 36 backend for pstore by default. This setting can be overridden
|
/linux-4.1.27/Documentation/mic/ |
D | mic_overview.txt | 31 the fact that the virtio block storage backend can only be on the host. 41 | Driver| |Driver | |Driver| | |backend | |backend | |backend |
|
/linux-4.1.27/fs/pstore/ |
D | platform.c | 69 static char *backend; variable 420 if (backend && strcmp(backend, psi->name)) in pstore_register() 546 module_param(backend, charp, 0444); 547 MODULE_PARM_DESC(backend, "Pstore backend to use");
|
/linux-4.1.27/Documentation/blockdev/ |
D | zram.txt | 25 Compression backend may use up to max_comp_streams compression streams, 27 By default, compression backend uses single compression stream. 37 In order to enable compression backend's multi stream support max_comp_streams 40 backend (max_comp_streams equals to 1), you will see error if you try to change 41 the value of max_comp_streams because single stream compression backend 43 dynamic max_comp_streams. Only multi stream backend supports dynamic
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | backend-api.txt | 17 cache the backend wants to make available. For instance, CacheFS does this in 31 (*) "ops" is a pointer to the table of operations that the backend supports on 117 The fields that might be of use to the backend describe the object 138 Structures of this type should be allocated by the cache backend and 187 backend to do the operation. The backend may get extra refs to it by 191 A retrieval operation can be used by the backend to do retrieval work. To 193 appropriately by the backend and fscache_enqueue_retrieval() called to 197 The to_do field is an empty list available for the cache backend to use as 219 The cache backend provides FS-Cache with a table of operations that can be 229 the backend. [all …]
|
D | object.txt | 30 a cache backend is currently actively caching. Such objects are represented by 150 from the cache backend's representation (fscache_object) - which may be 175 FS-Cache expects the cache backend to probe the cache to see whether this 286 the cache backend to update the object, and the cache backend will ask the 313 This is signalled when the cache backend wants to withdraw an object.
|
D | fscache.txt | 114 C, and that it should be read or written. The cache backend may or may 187 The cache backend API to FS-Cache can be found in: 189 Documentation/filesystems/caching/backend-api.txt
|
D | operations.txt | 31 backend for completion.
|
D | cachefiles.txt | 34 CacheFiles is a caching backend that's meant to use as a cache a directory on
|
/linux-4.1.27/net/atm/ |
D | ioctl.c | 137 atm_backend_t backend; in do_vcc_ioctl() local 138 error = get_user(backend, (atm_backend_t __user *)argp); in do_vcc_ioctl() 141 switch (backend) { in do_vcc_ioctl()
|
/linux-4.1.27/drivers/xen/ |
D | Kconfig | 100 Support for backend device drivers that provide I/O services 170 tristate "Xen PCI-device backend driver" 175 The PCI device backend driver allows the kernel to export arbitrary 185 The "hide" parameter (only applicable if backend driver is compiled 193 tristate "XEN SCSI backend driver" 196 The SCSI backend driver allows the kernel to export its SCSI Devices
|
/linux-4.1.27/Documentation/mic/mpssd/ |
D | mpssd.h | 80 int backend; member
|
D | mpssd.c | 968 mic->mic_virtblk.backend_size = lseek(mic->mic_virtblk.backend, 0, in set_backend_size() 991 mic->mic_virtblk.backend = open(mic->mic_virtblk.backend_file, O_RDWR); in open_backend() 992 if (mic->mic_virtblk.backend < 0) { in open_backend() 1002 mic->mic_virtblk.backend, 0L); in open_backend() 1012 close(mic->mic_virtblk.backend); in open_backend() 1023 close(mic->mic_virtblk.backend); in close_backend()
|
/linux-4.1.27/drivers/char/agp/ |
D | Makefile | 1 agpgart-y := backend.o frontend.o generic.o isoch.o
|
/linux-4.1.27/tools/perf/util/ |
D | parse-events.l | 181 stalled-cycles-backend|idle-cycles-backend { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_H…
|
/linux-4.1.27/drivers/crypto/caam/ |
D | Kconfig | 2 tristate "Freescale CAAM-Multicore driver backend" 15 tristate "Freescale CAAM Job Ring driver backend"
|
/linux-4.1.27/drivers/net/ethernet/seeq/ |
D | sgiseeq.c | 626 struct sgiseeq_tx_desc *backend; in sgiseeq_start_xmit() local 628 backend = &sp->tx_desc[PREV_TX(sp->tx_new)]; in sgiseeq_start_xmit() 629 dma_sync_desc_cpu(dev, backend); in sgiseeq_start_xmit() 630 backend->tdma.cntinfo &= ~HPCDMA_EOX; in sgiseeq_start_xmit() 631 dma_sync_desc_dev(dev, backend); in sgiseeq_start_xmit()
|
/linux-4.1.27/sound/core/ |
D | Kconfig | 105 tristate "HR-timer backend support" 109 Say Y here to enable HR-timer backend for ALSA timer. ALSA uses 121 Say Y here to use the HR-timer backend as the default sequencer
|
/linux-4.1.27/Documentation/tpm/ |
D | xen-tpmfront.txt | 72 * mini-os/tpmback: Mini-os TPM backend driver. The Linux frontend driver 73 connects to this backend driver to facilitate communications
|
/linux-4.1.27/drivers/vhost/ |
D | net.c | 1058 struct vhost_vring_file backend; in vhost_net_ioctl() local 1064 if (copy_from_user(&backend, argp, sizeof backend)) in vhost_net_ioctl() 1066 return vhost_net_set_backend(n, backend.index, backend.fd); in vhost_net_ioctl()
|
D | scsi.c | 1638 struct vhost_scsi_target backend; in vhost_scsi_ioctl() local 1649 if (copy_from_user(&backend, argp, sizeof backend)) in vhost_scsi_ioctl() 1651 if (backend.reserved != 0) in vhost_scsi_ioctl() 1654 return vhost_scsi_set_endpoint(vs, &backend); in vhost_scsi_ioctl() 1656 if (copy_from_user(&backend, argp, sizeof backend)) in vhost_scsi_ioctl() 1658 if (backend.reserved != 0) in vhost_scsi_ioctl() 1661 return vhost_scsi_clear_endpoint(vs, &backend); in vhost_scsi_ioctl()
|
/linux-4.1.27/drivers/char/pcmcia/ |
D | Kconfig | 31 or via the cm4000 backend of OpenCT (http://www.opensc-project.org/opensc).
|
/linux-4.1.27/drivers/cpuidle/ |
D | Kconfig.arm | 10 at run-time through DT nodes. The CPUidle suspend backend is
|
/linux-4.1.27/Documentation/input/ |
D | cs461x.txt | 13 driver as a backend. I've tested this driver with CS4610, 4-axis and
|
/linux-4.1.27/Documentation/device-mapper/ |
D | dm-crypt.txt | 41 This is the device that is going to be used as backend and contains the
|
/linux-4.1.27/drivers/pci/ |
D | Kconfig | 69 PCI devices from a PCI backend to support PCI driver domains.
|
/linux-4.1.27/drivers/net/ |
D | Kconfig | 345 The corresponding Linux backend driver is enabled by the 353 tristate "Xen backend network device" 364 The backend driver presents a standard network device
|
/linux-4.1.27/arch/powerpc/perf/ |
D | power7-pmu.c | 379 GENERIC_EVENT_ATTR(stalled-cycles-backend, PM_CMPLU_STALL);
|
/linux-4.1.27/Documentation/dvb/ |
D | bt8xx.txt | 32 Regular case: If the bttv driver detects a bt8xx-based DVB card, all frontend and backend modules w…
|
/linux-4.1.27/Documentation/ |
D | static-keys.txt | 259 <not supported> stalled-cycles-backend 276 <not supported> stalled-cycles-backend
|
D | workqueue.txt | 91 subsystems and drivers queue work items on and the backend mechanism
|
D | kernel-parameters.txt | 2960 pstore.backend= Specify the name of the pstore backend to use
|
/linux-4.1.27/drivers/block/ |
D | Kconfig | 507 tristate "Xen block-device backend driver" 510 The block-device backend driver allows the kernel to export its 517 The backend driver attaches itself to a any block device specified 521 If you are compiling a kernel to run in a Xen block backend driver
|
/linux-4.1.27/Documentation/filesystems/ |
D | 9p.txt | 77 cache backend.
|
/linux-4.1.27/Documentation/nfc/ |
D | nfc-hci.txt | 1 HCI backend for NFC Core 11 backend, implementing an abstract nfc device and translating NFC Core API
|
/linux-4.1.27/net/bridge/netfilter/ |
D | Kconfig | 220 as backend.
|
/linux-4.1.27/Documentation/networking/ |
D | phonet.txt | 194 PNPIPE_ENCAP_IP: The socket is used as a backend for a virtual IP
|
D | filter.txt | 577 an eBPF backend that performs almost as fast as natively compiled code. 581 GCC/LLVM backend, so that it can just-in-time map to modern 64-bit CPUs with
|
/linux-4.1.27/Documentation/sh/ |
D | new-machine.txt | 10 and the 2.5/2.6 SH backend.
|
/linux-4.1.27/Documentation/target/ |
D | tcmu-design.txt | 86 - Simple to write a userspace backend
|
/linux-4.1.27/drivers/tty/ |
D | Kconfig | 93 select the console driver that will serve as the backend for the
|
/linux-4.1.27/arch/x86/kernel/cpu/ |
D | perf_event.c | 1592 EVENT_ATTR(stalled-cycles-backend, STALLED_CYCLES_BACKEND );
|
/linux-4.1.27/init/ |
D | Kconfig | 561 context tracking backend but doesn't yet fullfill all the 571 architecture backend for the context tracking.
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 911 o slip - there is no particular reason to run the slip backend unless 1200 host. The TUN/TAP backend has been in UML since 2.4.9-3um. 4350 Yon Uriarte - Fixed the TUN/TAP network backend while I slept.
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 671 Paravirtualized spinlocks allow a pvops backend to replace the
|