Searched full:underlying (Results 1 – 25 of 743) sorted by relevance
12345678910>>...30
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | striped.rst | 6 device across one or more underlying devices. Data is written in "chunks",
7 with consecutive chunks rotating among the underlying devices. This can
13 Number of underlying devices.
18 Full pathname to the underlying block-device, or a
23 One or more underlying devices can be specified. The striped device size must
24 be a multiple of the chunk size multiplied by the number of underlying devices.
33 # Create a striped device across any number of underlying devices. The device
|
| D | dm-ebs.rst | 13 Underlying block size can be set to > 4K to test buffering larger units.
18 <dev path> <offset> <emulated sectors> [<underlying sectors>]
23 Full pathname to the underlying block-device,
43 offset 1024 sectors with underlying devices block size automatically set:
48 offset 128 sectors, enforce 2KiB underlying device block size.
|
| D | writecache.rst | 18 2. the underlying device that will be cached
48 underlying device
54 - some underlying devices perform better with fua, some
74 to the underlying device
|
| D | dm-flakey.rst | 15 underlying devices.
28 Full pathname to the underlying block-device, or a
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | overlayfs.rst | 32 In the special case of all overlay layers on the same underlying
34 filesystem and st_ino from the underlying filesystem. This will
40 underlying filesystem, the same compliant behavior could be achieved
42 identifier from the real object st_ino and an underlying fsid index.
44 If all underlying filesystems support NFS file handles and export file
46 will use the high inode number bits for fsid. Even when the underlying
49 case of underlying filesystems like xfs and tmpfs, which use 64bit inode
51 the underlying inode number does overflow into the high xino bits, overlay
187 underlying directory (upper or lower).
294 compared to direct access on underlying lower or upper filesystems
[all …]
|
| /Linux-v5.10/drivers/gpio/ |
| D | gpio-grgpio.c | 45 /* Structure for an irq of the core - called an underlying irq */
48 u8 uirq; /* Underlying irq of the gpio driver */
53 * used to map to the corresponding underlying irq.
68 * The grgpio core can have multiple "underlying" irqs. The gpio lines
69 * can be mapped to any one or none of these underlying irqs
76 * This array contains information on each underlying irq, each
85 * the irq to the underlying irq by pointing into the uirqs array.
205 * For each gpio line, call its interrupt handler if it its underlying in grgpio_irq_handler()
252 /* Request underlying irq if not already requested */ in grgpio_irq_map()
261 "Could not request underlying irq %d\n", in grgpio_irq_map()
[all …]
|
| /Linux-v5.10/drivers/md/ |
| D | dm-ebs-target.c | 23 struct dm_dev *dev; /* Underlying device to emulate block size on. */
31 unsigned int u_bs; /* Underlying block size in sectors retrievd from/set on lower layer device. */
33 bool u_bs_set:1; /* Flag to indicate underlying block size is set on table line. */
149 * Partial first underlying block (__nr_blocks() may have in __ebs_discard_bio()
157 /* Partial last underlying block if any. */ in __ebs_discard_bio()
239 * <dev_path>: path of the underlying device
242 * [<ubs>]: underlying block size in units of 512 bytes imposed on the lower layer;
243 * optional, if not supplied, retrieve logical block size from underlying device
283 ti->error = "Invalid underlying block size"; in ebs_ctr()
302 ti->error = "Invalid retrieved underlying block size"; in ebs_ctr()
[all …]
|
| /Linux-v5.10/include/drm/ |
| D | drm_simple_kms_helper.h | 59 * It is called when the underlying crtc is enabled.
69 * It is called when the underlying crtc is disabled.
78 * specifically when the underlying plane is checked.
97 * This function is called when the underlying plane state is updated.
|
| /Linux-v5.10/drivers/net/ipa/ |
| D | ipa_interrupt.h | 22 * for an AP RX endpoint whose underlying GSI channel is suspended/stopped.
70 * be delivered to the endpoint because it is suspended (or its underlying
98 * that occurs if aggregation is active on an endpoint when its underlying
|
| /Linux-v5.10/arch/m68k/include/asm/ |
| D | timex.h | 12 * CLOCK_TICK_RATE should give the underlying frequency of the tick timer
22 #define CLOCK_TICK_RATE 1193180 /* Underlying HZ */
|
| /Linux-v5.10/include/linux/iio/ |
| D | sysfs.h | 16 * @dev_attr: underlying device attribute
19 * @c: specification for the underlying channel
39 * @dev_attr: underlying device attribute
|
| /Linux-v5.10/include/linux/ |
| D | hwspinlock.h | 171 * This function attempts to lock the underlying hwspinlock, and will
192 * This function attempts to lock the underlying hwspinlock, and will
269 * This function locks the underlying @hwlock. If the @hwlock
292 * This function locks the underlying @hwlock. If the @hwlock
315 * This function locks the underlying @hwlock. If the @hwlock
338 * This function locks the underlying @hwlock. If the @hwlock
360 * This function locks the underlying @hwlock. If the @hwlock
|
| D | device-mapper.h | 102 * properties of underlying devices.
103 * E.g. Does at least one underlying device support flush?
104 * Does any underlying device not support WRITE_SAME?
107 * an underlying device. State can be maintained in *data.
277 * to the real underlying devices.
319 * whether or not its underlying devices have support.
325 * whether or not its underlying devices have support.
|
| /Linux-v5.10/include/xen/interface/io/ |
| D | blkif.h | 89 * the underlying block-device hardware. The boolean simply indicates whether
98 * info. A flush will ask the underlying storage hardware to flush its
102 * with BLKIF_RSP_EOPNOTSUPP if it is unsupported by the underlying
116 * the underlying block-device hardware. The boolean simply indicates whether
121 * Discard operation is a request for the underlying block device to mark
129 * underlying block device supports trim (ATA) or unmap (SCSI) operations,
|
| /Linux-v5.10/Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 10 underlying SCSI LUNs that are shared with the client.
21 option and the underlying SCSI device support persistent reservations.
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | pstore | 27 the file will signal to the underlying persistent storage
39 multiple) files based on the record size of the underlying
|
| /Linux-v5.10/fs/ocfs2/ |
| D | stackglue.h | 7 * Glue to the underlying cluster stack.
91 * state for the underlying stack. ocfs2 does use cc_version to determine
156 * Call the underlying dlm lock function. The ->dlm_lock()
173 * Call the underlying dlm unlock function. The ->dlm_unlock()
|
| /Linux-v5.10/Documentation/locking/ |
| D | futex-requeue-pi.rst | 6 special handling in order to ensure the underlying rt_mutex is never
50 underlying rt_mutex with waiters, and no owner, breaking the
120 task as a waiter on the underlying rt_mutex. It is possible that
|
| D | hwspinlock.rst | 400 To be called from the underlying platform-specific implementation, in
411 To be called from the underlying vendor-specific implementation, in order
424 of hardware locks. It is registered by the underlying hwspinlock
431 * @dev: underlying device, will be used to invoke runtime PM api
452 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
484 spinning on a lock, and can be used by the underlying implementation to force
|
| /Linux-v5.10/drivers/staging/gasket/ |
| D | gasket_sysfs.h | 48 /* The underlying sysfs device attribute associated with this data. */
130 * underlying device sysfs information/structure will remain valid/will not be
151 * gasket_sysfs_put_attr. While this reference is held, the underlying device
|
| /Linux-v5.10/include/uapi/linux/ |
| D | vm_sockets.h | 24 * specifies the size of the buffer underlying a vSockets STREAM socket.
32 * specifies the minimum size allowed for the buffer underlying a vSockets
40 * that specifies the maximum size allowed for the buffer underlying a
|
| D | ip6_tunnel.h | 29 int link; /* ifindex of underlying L2 interface */
41 int link; /* ifindex of underlying L2 interface */
|
| /Linux-v5.10/drivers/hwspinlock/ |
| D | hwspinlock_internal.h | 38 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
48 * @dev: underlying device, will be used to invoke runtime PM api
|
| /Linux-v5.10/Documentation/virt/kvm/devices/ |
| D | xive.rst | 11 interface to configure the interrupt sources of a VM in the underlying
119 -ENXIO Could not allocate underlying HW interrupt
147 underlying HW interrupt failed
192 -EIO Configuration of the underlying HW failed
|
| /Linux-v5.10/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 91 * ``drop``: Trapped packets were dropped by the underlying device. Packets
95 underlying device due to an exception (e.g., TTL error, missing neighbour
115 * ``drop``: The packet is dropped by the underlying device and a copy is not
117 * ``mirror``: The packet is forwarded by the underlying device and a copy is
586 As previously explained, the underlying device can trap certain packets to the
587 CPU for processing. In most cases, the underlying device is capable of handling
591 Therefore, in order to prevent the underlying device from overwhelming the CPU,
|
12345678910>>...30
