Searched refs:underlying (Results 1 – 25 of 199) sorted by relevance
12345678
| /linux-6.1.9/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 | 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 | 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 | unstriped.rst | 9 unstripe a device-mapper "striped" target to access the underlying disks
41 underlying device on the striped array::
|
| D | linear.rst | 11 Full pathname to the underlying block-device, or a
|
| /linux-6.1.9/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 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
187 underlying directory (upper or lower).
294 compared to direct access on underlying lower or upper filesystems
302 upper layer based on underlying filesystem permissions, again including
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-usi.yaml | 66 Enable this property if underlying protocol requires the clock to be
77 description: Child node describing underlying I2C
81 description: Child node describing underlying UART/serial
85 description: Child node describing underlying SPI
|
| /linux-6.1.9/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-caps | 13 like Intel is pmu_name, which exposes underlying CPU name known
|
| D | configfs-stp-policy-p_sys-t | 20 if the underlying transport protocol supports marking message
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/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-6.1.9/drivers/staging/olpc_dcon/ |
| D | TODO | 3 1. The underlying fbdev drivers need to be converted into drm kernel
|
| /linux-6.1.9/scripts/ |
| D | subarch.include | 1 # SUBARCH tells the usermode build what the underlying arch is. That is set
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/block/ |
| D | writeback_cache_control.rst | 45 worry if the underlying devices need any explicit cache flushing and how
55 bits need to be propagated to underlying devices, and a global flush needs
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/Documentation/devicetree/bindings/leds/backlight/ |
| D | led-backlight.yaml | 32 accepted by the underlying LED devices. This is used to translate a
|
| /linux-6.1.9/fs/proc/ |
| D | Kconfig | 55 underlying devices are initialized in crash recovery kernel.
57 recovery kernel's initramfs to collect its underlying device
|
| /linux-6.1.9/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
596 As previously explained, the underlying device can trap certain packets to the
597 CPU for processing. In most cases, the underlying device is capable of handling
601 Therefore, in order to prevent the underlying device from overwhelming the CPU,
|
12345678