| /Documentation/admin-guide/device-mapper/ |
| D | dm-clone.rst | 58 3. A small metadata device - it records which regions are already valid in the
59 destination device, i.e., which regions have already been hydrated, or have
65 Regions section in Design
68 dm-clone divides the source and destination devices in fixed sized regions.
69 Regions are the unit of hydration, i.e., the minimum amount of data copied from
77 Reads and writes from/to hydrated regions are serviced from the destination
93 as a hint to skip hydration of the regions covered by the request, i.e., it
111 A message `hydration_threshold <#regions>` can be used to set the maximum number
112 of regions being copied, the default being 1 region.
116 region size. A message `hydration_batch_size <#regions>` can be used to tune the
[all …]
|
| D | statistics.rst | 6 regions of a DM device. If no regions are defined no statistics are
117 List all regions registered with @stats_create.
121 If this parameter is specified, only matching regions
123 If it is not specified, all regions are returned.
|
| D | switch.rst | 6 arbitrary mapping of fixed-size regions of I/O across a fixed set of
11 number of fixed-sized address regions but there is no simple pattern
42 A device-mapper table already lets you map different regions of a
96 Modify the region table by specifying which regions are redirected to
|
| /Documentation/devicetree/bindings/pci/ |
| D | cdns,cdns-pcie-ep.txt | 8 - cdns,max-outbound-regions: Set to maximum number of outbound regions
23 cdns,max-outbound-regions = <16>;
|
| D | cdns,cdns-pcie-host.txt | 14 - ranges: Ranges for the PCI memory and I/O regions
20 - cdns,max-outbound-regions: Set to maximum number of outbound regions
40 cdns,max-outbound-regions = <16>;
|
| D | rockchip-pcie-ep.txt | 34 - rockchip,max-outbound-regions: Maximum number of outbound regions
44 rockchip,max-outbound-regions = <16>;
|
| D | xgene-pci.txt | 14 - ranges: ranges for the outbound memory, I/O regions.
15 - dma-ranges: ranges for the inbound memory regions.
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 1 *** Reserved memory regions ***
6 normal use) memory regions. Such memory regions are usually designed for
21 Each child of the reserved-memory node specifies one or more regions of
41 - Specifies regions of memory that are
76 Regions in the /reserved-memory node may be referenced by other device
83 This example defines 3 contiguous regions are defined for Linux kernel:
|
| D | xen,shared-memory.txt | 3 Expose one or more memory regions as reserved-memory to the guest
8 For each of these pre-shared memory regions, a range is exposed under
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom,spmi-pmic.txt | 7 locations/definitions within these regions, with some of these regions
13 16-bit SPMI slave address space into 256 smaller fixed-size regions, 256 bytes
14 each. A function can consume one or more of these fixed-size register regions.
|
| /Documentation/devicetree/bindings/pmem/ |
| D | pmem-region.txt | 1 Device-tree bindings for persistent memory regions
11 persistent regions separately to the normal memory pool. To aid with that this
13 memory regions exist inside the physical address space.
56 * This node specifies two 4KB regions that are backed by
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-iommu_groups | 21 regions that are reserved. Not necessarily all
22 reserved regions are listed. This is typically used to
23 output direct-mapped, MSI, non mappable regions. Each
|
| /Documentation/x86/ |
| D | intel-iommu.rst | 30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
|
| /Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.txt | 18 FPGA Regions represent FPGA's and partial reconfiguration regions of FPGA's in
19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree
55 * A persona may create more regions.
65 will be used to gate the busses. Traffic to other regions is not affected.
69 * An FPGA image may create a set of reprogrammable regions, each having its
79 * A base image may set up a set of partial reconfiguration regions that may
99 Figure 1: An FPGA set up with a base image that created three regions. Each
124 FPGA Regions represent FPGA's and FPGA PR regions in the device tree. An FPGA
151 These FPGA regions are children of FPGA bridges which are then children of the
160 FPGA Regions do not inherit their ancestor FPGA regions' bridges. This prevents
[all …]
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | mdp5.txt | 14 - reg-names: The names of register regions. The following regions are required:
41 - reg-names: The names of register regions. The following regions are required:
|
| D | edp.txt | 7 - reg-names: The names of register regions. The following regions are required:
|
| D | hdmi.txt | 42 - reg-names: The names of register regions. The following regions are required:
45 For HDMI PHY on msm8996, these additional register regions are required:
|
| /Documentation/admin-guide/mm/ |
| D | transhuge.rst | 79 MADV_HUGEPAGE madvise regions.
81 Embedded systems should enable hugepages only inside madvise regions
87 madvise(MADV_HUGEPAGE) on their critical mmapped regions.
99 regions (to avoid the risk of consuming more memory resources) or enabled
108 regions or to never try to defrag memory and simply fallback to regular
138 only for regions that have used madvise(MADV_HUGEPAGE); all
139 other regions will wake kswapd in the background to reclaim
144 will enter direct reclaim like ``always`` but only for regions
276 regions registered in khugepaged.
|
| D | soft-dirty.rst | 40 memory region renewal the kernel always marks new memory regions (and
41 expanded regions) as soft dirty.
|
| /Documentation/driver-api/ |
| D | zorro.rst | 72 The address regions in the Zorro device resources are Zorro bus address
73 regions. Due to the identity bus-physical address mapping on the Zorro bus,
76 The treatment of these regions depends on the type of Zorro space:
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 14 The QMSS driver manages the PDSP setups, linking RAM regions,
35 Register regions should be specified in the following
91 - descriptor-regions : child node describing the memory regions for keystone
107 Register regions should be specified in the following
216 descriptor-regions {
|
| D | keystone-navigator-dma.txt | 43 register regions. Register regions should be specified in the following
52 - reg-names: Names for the register regions.
|
| /Documentation/devicetree/bindings/display/ |
| D | zte,vou.txt | 22 - reg: Physical base address and length of DPC register regions, one for each
24 - reg-names: The names of register regions. The following regions are required:
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | wkup_m3_rproc.txt | 22 memory regions, UMEM and DMEM. The parent node should
26 regions. These should be named "umem" & "dmem".
|
| /Documentation/devicetree/bindings/mtd/ |
| D | stm32-fmc2-nand.txt | 9 Regions 2 to 4 respectively contain the data, command,
11 Regions 5 to 7 contain the same areas for CS1.
|