Searched full:underlying (Results 1 – 25 of 213) sorted by relevance
123456789
| /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,
34 <underlying sectors>:
43 offset 1024 sectors with underlying devices block size automatically set:
48 offset 128 sectors, enforce 2KiB underlying device block size.
|
| D | writecache.rst | 17 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
|
| D | dm-flakey.rst | 15 underlying devices.
28 Full pathname to the underlying block-device, or a
|
| D | vdo.rst | 120 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
|
| /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 number.
44 underlying filesystems rarely use the high inode number bits. In case
45 the underlying inode number does overflow into the high xino bits, overlay
49 If all underlying filesystems support NFS file handles, the value of st_ino
196 underlying directory (upper or lower).
302 compared to direct access on underlying lower or upper filesystems
310 upper layer based on underlying filesystem permissions, again including
[all …]
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 7 utility over the underlying device.
17 propagated to the underlying device.
19 State 1: All writes to the device cause the underlying data to be backed up to
34 dm-bow takes one command line parameter, the name of the underlying device.
37 suitable underlying device and the resultant device will be mounted. A file
|
| /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.
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-intel-m10-bmc-sec-update | 8 visible if the underlying device supports it.
18 is only visible if the underlying device supports it.
28 underlying device supports it.
|
| D | pstore | 28 the file will signal to the underlying persistent storage
40 multiple) files based on the record size of the underlying
|
| D | sysfs-bus-event_source-devices-hv_gpci | 103 underlying platform/firmware.
135 underlying platform/firmware.
167 underlying platform/firmware.
199 underlying platform/firmware.
231 underlying platform/firmware.
|
| D | debugfs-scmi | 5 Description: The name of the underlying SCMI instance <n> described by
34 Description: A boolean stating if the transport configured on the underlying
|
| D | sysfs-bus-event_source-devices-caps | 13 like Intel is pmu_name, which exposes underlying CPU name known
|
| /Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-usi.yaml | 74 Enable this property if underlying protocol requires the clock to be
85 description: Child node describing underlying I2C
89 description: Child node describing underlying UART/serial
93 description: Child node describing underlying SPI
|
| /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 | 411 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
|
| /Documentation/admin-guide/perf/ |
| D | arm-cmn.rst | 38 match the underlying pmu_event0_id encoding for the pmu_event_sel
53 Since the watchpoint direction is otherwise implicit in the underlying
|
| D | arm-ni.rst | 9 exist within a system, the PMU devices can be correlated with the underlying
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 18 control of the underlying resources as well as to allow the provider to
56 will have any effect as there may be multiple users of the underlying resources
|
| /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
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 13 LIRC_GET_FEATURES - Get the underlying hardware device's features
34 Get the underlying hardware device's features. If a driver does not
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 45 worry if the underlying devices need any explicit cache flushing and how
81 For remapping drivers the REQ_FUA bits need to be propagated to underlying
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 47 Count of bad physical eraseblocks on the underlying MTD device.
101 Number of the underlying MTD device.
125 the underlying MTD device.
|
| /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
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,
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 94 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
|
123456789