/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A 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
|
H A D | dm-ebs.rst | 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 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
|
H A D | dm-flakey.rst | 15 underlying devices. 28 Full pathname to the underlying block-device, or a
|
H A D | unstriped.rst | 9 unstripe a device-mapper "striped" target to access the underlying disks 41 underlying device on the striped array::
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/composefs/ |
H A D | composefs_1.0.8.bb | 2 DESCRIPTION = "The composefs project combines several underlying Linux \ 4 filesystem trees, stacking on top of an underlying "lower" Linux filesystem."
|
/openbmc/linux/Documentation/filesystems/ |
H A 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). 293 compared to direct access on underlying lower or upper filesystems 301 upper layer based on underlying filesystem permissions, again including [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A 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.
|
H A D | pstore | 28 the file will signal to the underlying persistent storage 40 multiple) files based on the record size of the underlying
|
H A 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.
|
H A 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
|
H A D | sysfs-bus-event_source-devices-caps | 13 like Intel is pmu_name, which exposes underlying CPU name known
|
/openbmc/linux/Documentation/admin-guide/nfs/ |
H A 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.
|
/openbmc/linux/Documentation/virt/kvm/devices/ |
H A 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
|
/openbmc/linux/Documentation/locking/ |
H A 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
|
H A 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
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/files/ |
H A D | 0001-Allow-configuring-flash-image-files-compile-time.patch | 41 /* Initialise a file_block_store to provide underlying storage */ 74 /* Initialise a semihosting_block_store to provide underlying storage */
|
/openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
H A D | image_types_sparse.bbclass | 5 # underlying image's block size will not result in any further space saving.
|
/openbmc/linux/drivers/staging/olpc_dcon/ |
H A D | TODO | 3 1. The underlying fbdev drivers need to be converted into drm kernel
|
/openbmc/linux/Documentation/userspace-api/media/rc/ |
H A 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
|
/openbmc/linux/scripts/ |
H A D | subarch.include | 1 # SUBARCH tells the usermode build what the underlying arch is. That is set
|
/openbmc/linux/Documentation/admin-guide/perf/ |
H A 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
|
/openbmc/u-boot/drivers/tee/optee/ |
H A D | Kconfig | 8 ARM TrustZone(R) technology as the underlying hardware isolation
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | arch.rst | 14 has started to converge on a 'core' set of underlying mechanisms:
|
/openbmc/openbmc/poky/meta/recipes-devtools/perl/ |
H A D | libxml-simple-perl_2.25.bb | 3 on top of an underlying XML parsing module to maintain XML files \
|