Home
last modified time | relevance | path

Searched full:underlying (Results 1 – 25 of 795) sorted by relevance

12345678910>>...32

/linux/Documentation/admin-guide/device-mapper/
H A Dstriped.rst6 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
H A Ddm-ebs.rst13 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,
34 <underlying sectors>:
43 offset 1024 sectors with underlying devices block size automatically set:
48 offset 128 sectors, enforce 2KiB underlying device block size.
H A Dwritecache.rst17 2. the underlying device that will be cached
47 underlying device
53 - some underlying devices perform better with fua, some
69 written to the underlying device and cleaned up.
105 to the underlying device
H A Dvdo.rst120 The number of threads used to issue bios to the underlying
146 underlying storage device. At format time, a slab size for
186 underlying storage device. Additionally, when formatting the vdo device, a
349 Because the underlying storage may be multiply referenced, over-writing
360 - Assuming the underlying storage properly implements flush requests, vdo
396 the underlying storage; fewer threads mean there is more opportunity to
/linux/drivers/md/
H A Ddm-ebs-target.c24 struct dm_dev *dev; /* Underlying device to emulate block size on. */
32 …unsigned int u_bs; /* Underlying block size in sectors retrieved from/set on lower layer device. …
34 bool u_bs_set:1; /* Flag to indicate underlying block size is set on table line. */
151 * Partial first underlying block (__nr_blocks() may have in __ebs_discard_bio()
159 /* Partial last underlying block if any. */ in __ebs_discard_bio()
241 * <dev_path>: path of the underlying device
244 * [<ubs>]: underlying block size in units of 512 bytes imposed on the lower layer;
245 * optional, if not supplied, retrieve logical block size from underlying device
285 ti->error = "Invalid underlying block size"; in ebs_ctr()
304 ti->error = "Invalid retrieved underlying block size"; in ebs_ctr()
[all …]
/linux/security/landlock/
H A Dobject.h19 * struct landlock_object_underops - Operations on an underlying object
23 * @release: Releases the underlying object (e.g. iput() for an inode).
59 * tied to its underlying kernel structure. This pointer is protected
73 * underlying object (e.g. inode).
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-event_source-devices-hv_gpci103 underlying platform/firmware.
135 underlying platform/firmware.
167 underlying platform/firmware.
199 underlying platform/firmware.
231 underlying platform/firmware.
H A Dsysfs-driver-intel-m10-bmc-sec-update8 visible if the underlying device supports it.
18 is only visible if the underlying device supports it.
28 underlying device supports it.
H A Dpstore28 the file will signal to the underlying persistent storage
40 multiple) files based on the record size of the underlying
/linux/include/linux/
H A Dhwspinlock.h177 * This function attempts to lock the underlying hwspinlock, and will
198 * This function attempts to lock the underlying hwspinlock, and will
275 * This function locks the underlying @hwlock. If the @hwlock
298 * This function locks the underlying @hwlock. If the @hwlock
321 * This function locks the underlying @hwlock. If the @hwlock
344 * This function locks the underlying @hwlock. If the @hwlock
366 * This function locks the underlying @hwlock. If the @hwlock
H A Ddevice-mapper.h113 * properties of underlying devices.
114 * E.g. Does at least one underlying device support flush?
115 * Does any underlying device not support WRITE_SAME?
118 * an underlying device. State can be maintained in *data.
322 * to the real underlying devices.
358 * whether or not its underlying devices have support.
364 * whether or not its underlying devices have support.
410 * targets in a table use the same underlying device.
413 * flushes to the underlying devices without performing any other
/linux/include/xen/interface/io/
H A Dblkif.h89 * 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/arch/m68k/include/asm/
H A Dtimex.h12 * CLOCK_TICK_RATE should give the underlying frequency of the tick timer
22 #define CLOCK_TICK_RATE 1193180 /* Underlying HZ */
/linux/include/linux/iio/
H A Dsysfs.h17 * @dev_attr: underlying device attribute
20 * @c: specification for the underlying channel
42 * @dev_attr: underlying device attribute
/linux/Documentation/admin-guide/nfs/
H A Dpnfs-scsi-server.rst10 underlying SCSI LUNs that are shared with the client.
21 option and the underlying SCSI device support persistent reservations.
/linux/include/drm/
H A Ddrm_simple_kms_helper.h59 * 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/fs/ocfs2/
H A Dstackglue.h5 * Glue to the underlying cluster stack.
89 * state for the underlying stack. ocfs2 does use cc_version to determine
154 * Call the underlying dlm lock function. The ->dlm_lock()
171 * Call the underlying dlm unlock function. The ->dlm_unlock()
/linux/Documentation/locking/
H A Dhwspinlock.rst411 To be called from the underlying platform-specific implementation, in
422 To be called from the underlying vendor-specific implementation, in order
435 of hardware locks. It is registered by the underlying hwspinlock
442 * @dev: underlying device, will be used to invoke runtime PM api
463 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
495 spinning on a lock, and can be used by the underlying implementation to force
H A Dfutex-requeue-pi.rst6 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
/linux/include/uapi/linux/
H A Dip6_tunnel.h29 int link; /* ifindex of underlying L2 interface */
41 int link; /* ifindex of underlying L2 interface */
/linux/Documentation/networking/devlink/
H A Ddevlink-trap.rst91 * ``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
609 As previously explained, the underlying device can trap certain packets to the
610 CPU for processing. In most cases, the underlying device is capable of handling
614 Therefore, in order to prevent the underlying device from overwhelming the CPU,
/linux/Documentation/virt/kvm/devices/
H A Dxive.rst11 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/fs/9p/
H A Dfid.h44 * make sure mode reflects flags of underlying mounts
47 * underlying file system on server.
/linux/drivers/hwspinlock/
H A Dhwspinlock_internal.h41 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
51 * @dev: underlying device, will be used to invoke runtime PM api
/linux/Documentation/userspace-api/
H A Ddma-buf-alloc-exchange.rst94 Each buffer must have an underlying format. This format describes the color
151 underlying memory storage. For example, even though a 1920x1080
157 base address of the underlying memory, nor is it guaranteed that the memory
244 allocation, any padding required, and further properties of the underlying
327 should use its own logic to determine what the underlying layout may be.
350 that the underlying layout is implementation-defined and that an explicit

12345678910>>...32