Searched full:zones (Results 1 – 25 of 54) sorted by relevance
123
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
26 instance is at most 4.5 MB and as little as 5 zones will be used
38 write accesses to the sequential zones of a zoned block device.
39 Conventional zones are used for caching as well as for storing internal
42 in zones with the same size as the zoned block device. These zones will be
43 placed in front of the zones from the zoned block device and will be handled
44 just like conventional zones.
46 The zones of the device(s) are separated into 2 types:
48 1) Metadata zones: these are conventional zones used to store metadata.
49 Metadata zones are not reported as usable capacity to the user.
[all …]
|
| D | vdo-design.rst | 33 Zones and Threading
44 "zones" such that any given bio must only access a single zone of any zoned
58 Although each structure is divided into zones, this division is not
60 the number of zones for each structure, and hence the number of threads,
249 zones" in round-robin fashion. If there are P physical zones, then slab n
280 There are 60 radix trees which are assigned to "logical zones" in round
281 robin fashion. (If there are L logical zones, tree n will belong to zone n
408 free block or runs out of zones to search. The data_vio will acquire a
558 are in different zones, they are made concurrently, and if they are in
|
| /Documentation/filesystems/ |
| D | zonefs.rst | 14 write zones of the device must be written sequentially starting from the end
34 space that is divided into zones. A zone is a group of consecutive LBAs and all
35 zones are contiguous (there are no LBA gaps). Zones may have different types.
37 * Conventional zones: there are no access constraints to LBAs belonging to
38 conventional zones. Any read or write access can be executed, similarly to a
40 * Sequential zones: these zones accept random reads but must be written
44 cannot be overwritten. Sequential zones must first be erased using a special
60 Zonefs exposes the zones of a zoned block device as files. The files
61 representing zones are grouped by zone type, which are themselves represented
85 Files representing zones of the same type are grouped together under the same
[all …]
|
| /Documentation/mm/ |
| D | balance.rst | 41 zone size (and possibly of the size of lower class zones), we can decide
44 of lower class zones, the bad part is, we might do too frequent balancing
45 due to ignoring possibly lower usage in the lower class zones. Also,
50 of a zone _and_ all its lower class zones falls below 1/64th of the
51 total memory in the zone and its lower class zones. This fixes the 2.2
54 which have different numbers and types of zones. If we wanted to get
56 zones in the future.
72 kswapd also needs to know about the zones it should balance. kswapd is
|
| D | physical_memory.rst | 33 called zones which represent ranges within memory. These ranges are usually
48 both zones as they support peripherals with different DMA addressing
78 ``ZONE_NORMAL`` so it is the most performance critical zone. Zones are
79 discussed further in Section :ref:`Zones <zones>`.
86 entire memory will be on node 0 and there will be three zones: ``ZONE_DMA``,
212 The zones for this node. Not all of the zones may be populated, but it is
217 The list of all zones in all nodes. This list defines the order of zones
223 Number of populated zones in this node.
339 Zones chapter
|
| D | numa.rst | 74 an ordered "zonelist". A zonelist specifies the zones/nodes to visit when a
79 Because some nodes contain multiple zones containing different types of
82 type on the same node. This is an important consideration because some zones,
84 a default Node ordered zonelist. This means it tries to fallback to other zones
92 nodes' zones in the selected zonelist looking for the first zone in the list
118 zones [nodes] with memory in the zonelists. This means that for a memoryless
|
| /Documentation/power/powercap/ |
| D | powercap.rst | 19 Power zones represent different parts of the system, which can be controlled and
23 the system represented by different power zones are hierarchical (that is, one
25 controls), those power zones may also be organized in a hierarchy with one
150 control type called intel-rapl which contains two power zones, intel-rapl:0 and
151 intel-rapl:1, representing CPU packages. Each of these power zones contains
154 the zones and subzones contain energy monitoring attributes (energy_uj,
156 to be applied (the constraints in the 'package' power zones apply to the whole
170 Depending on different power zones, the Intel RAPL technology allows
173 All the zones contain attributes representing the constraint names,
245 enabled (rw): Enable/Disable controls at zone level or for all zones using
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-sensor.yaml | 15 and the software abstraction of thermal zones required to take appropriate
22 - thermal-zones: a container of the following node types used to describe all
28 zones. Typical devices are I2C ADC converters and bandgaps. Thermal sensor
|
| D | thermal-zones.yaml | 5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml#
15 and the software abstraction of cooling devices and thermal zones required to
22 - thermal-zones: a container of the following node types used to describe all
25 This binding describes the thermal-zones.
42 const: thermal-zones
44 A /thermal-zones node is required in order to use the thermal framework to
45 manage input from the various thermal zones in the system in order to
277 thermal-zones {
|
| D | thermal-cooling-devices.yaml | 15 and the software abstraction of cooling devices and thermal zones required to
22 - thermal-zones: a container of the following node types used to describe all
96 thermal-zones {
|
| D | amazon,al-thermal.txt | 18 thermal-zones {
|
| D | brcm,ns-thermal.yaml | 42 thermal-zones {
|
| D | st,stm32-thermal.yaml | 56 thermal-zones {
|
| D | rzg2l-thermal.yaml | 65 thermal-zones {
|
| D | max77620_thermal.txt | 41 thermal-zones {
|
| D | qcom,spmi-temp-alarm.yaml | 64 thermal-zones {
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 370 multiple zones or spans multiple nodes; such memory blocks
406 using the ``contig-zones`` online policy. When
408 onlining a memory block, unless other zones can be kept
460 ``contig-zones`` has been the kernel default
466 When set to ``contig-zones``, the kernel will
467 try keeping zones contiguous. If a memory block
468 intersects multiple zones or no zone, the
513 in the zones combined with accounting per
516 residing on one of the kernel zones. The
557 kernel zones can increase the number of possible transparent huge pages and
[all …]
|
| D | concepts.rst | 97 Zones chapter
105 groups memory pages into `zones` according to their possible
111 The actual layout of the memory zones is hardware dependent as not all
112 architectures define all zones, and requirements for DMA are different
123 own set of zones, lists of free and used pages and various statistics
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 17 controlled. A <control type> can contain multiple power zones.
42 Power zones may be organized in a hierarchy in which child
43 power zones provide monitoring and control for a subset of
|
| D | sysfs-devices-memory | 78 provided by a memory block is managed. If multiple zones
86 the kernel zones (DMA, DMA32, Normal) is applicable for a single
|
| D | sysfs-bus-iio-light-lm3533-als | 34 zones.
|
| /Documentation/devicetree/bindings/reset/ |
| D | brcm,bcm63138-pmb.txt | 12 by the phandle, and the second is the number of zones for this peripheral
|
| /Documentation/devicetree/bindings/display/ |
| D | repaper.txt | 31 thermal-zones {
|
| /Documentation/hwmon/ |
| D | asc7621.rst | 51 We offer flexible mapping of temperature readings to thermal zones. Any
56 a set of zones to control the PWM of an individual fan, but there is no
91 Using temperature information from these four zones, an automatic fan speed
97 temperature zones. Both high- and low-frequency PWM ranges are supported.
223 Only the following combination of zones (and their corresponding masks)
|
| /Documentation/arch/powerpc/ |
| D | kaslr-booke32.rst | 25 image. The memory will be split in 64M zones. We will use the lower 8
|
123