Searched full:zone (Results 1 – 25 of 83) sorted by relevance
1234
| /Documentation/filesystems/ |
| D | zonefs.rst | 4 ZoneFS - Zone filesystem for Zoned block devices
10 zonefs is a very simple file system exposing each zone of a zoned block device
24 by allowing SSTables to be stored in a zone file similarly to a regular file
26 of the higher level construct "one file is one zone" can help reducing the
34 space that is divided into zones. A zone is a group of consecutive LBAs and all
41 sequentially. Each sequential zone has a write pointer maintained by the
43 to the device. As a result of this write constraint, LBAs in a sequential zone
45 command (zone reset) before rewriting.
61 representing zones are grouped by zone type, which are themselves represented
62 by sub-directories. This file structure is built entirely using zone information
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 54 Data in these zones may be directly mapped to the conventional zone, but
55 later moved to a sequential zone so that the conventional zone can be
65 1) The first block of the first conventional zone found contains the
73 indicates the zone number of the device storing the chunk of data. Each
74 mapping entry may also indicate if the zone number of a conventional
75 zone used to buffer random modification to the data zone.
80 data chunk, a block is always valid only in the data zone mapping the
81 chunk or in the buffer zone of the chunk.
83 For a logical chunk mapped to a conventional zone, all write operations
84 are processed by directly writing to the zone. If the mapping zone is a
[all …]
|
| D | vdo-design.rst | 44 "zones" such that any given bio must only access a single zone of any zoned
46 normal operation, each zone is assigned to a specific thread, and only that
47 thread will access the portion of the data structure in that zone.
51 zone associated with that queue.
54 each zone has an implicit lock on the structures it manages for all its
250 is assigned to zone n mod P.
257 how full it is. During recovery, each physical zone will attempt to recover
259 free blocks. Once each zone has some space, or has determined that none is
281 robin fashion. (If there are L logical zones, tree n will belong to zone n
285 Choosing 60 trees results in an evenly distributed number of trees per zone
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 25 This status affects every power zone using this "control_type.
27 What: /sys/class/powercap/<control type>/<power zone>
32 A power zone is a single or a collection of devices, which can
33 be independently monitored and controlled. A power zone sysfs
37 What: /sys/class/powercap/<control type>/<power zone>/<child power zone>
45 power zone for a whole CPU package, each CPU core in it can
46 be a child power zone.
48 What: /sys/class/powercap/.../<power zone>/name
53 Specifies the name of this power zone.
55 What: /sys/class/powercap/.../<power zone>/energy_uj
[all …]
|
| D | sysfs-class-thermal | 3 Strings which represent the thermal zone type.
4 This is given by thermal zone driver as part of registration.
14 Current temperature as reported by thermal zone (sensor).
24 currently managing the thermal zone. It can be either default
30 Preventing kernel thermal zone driver actions upon
38 One of the various thermal governors used for a particular zone.
45 particular zone.
62 for ACPI thermal zone.
84 The trip point in this thermal zone which `cdev[0-*]` is
92 The influence of `cdev[0-*]` in this thermal zone. This value
[all …]
|
| D | sysfs-class-backlight | 88 What: /sys/class/backlight/<backlight>/<ambient light zone>_max
93 Control the maximum brightness for <ambient light zone>
96 <ambient light zone>.
98 The <ambient light zone> is device-driver specific:
100 For ADP5520 and ADP5501, <ambient light zone> can be:
104 light zone
111 For ADP8860, <ambient light zone> can be:
115 light zone
122 For ADP8870, <ambient light zone> can be:
126 light zone
[all …]
|
| D | sysfs-bus-iio-light-lm3533-als | 7 in each direction (rising|falling) and a zone change occurs.
8 The corresponding light zone can be read from
32 These thresholds correspond to the eight zone-boundary
41 Get the current light zone (0..4) as defined by the
49 Set the output current for channel out_currentY when in zone
56 current zone.
|
| D | sysfs-class-backlight-driver-lm3533 | 48 bit 5 PWM-input enabled in Zone 4
49 bit 4 PWM-input enabled in Zone 3
50 bit 3 PWM-input enabled in Zone 2
51 bit 2 PWM-input enabled in Zone 1
52 bit 1 PWM-input enabled in Zone 0
|
| D | sysfs-class-led-driver-lm3533 | 67 bit 5 PWM-input enabled in Zone 4
68 bit 4 PWM-input enabled in Zone 3
69 bit 3 PWM-input enabled in Zone 2
70 bit 2 PWM-input enabled in Zone 1
71 bit 1 PWM-input enabled in Zone 0
|
| D | sysfs-devices-memory | 56 when onlining to select a target zone: "online_movable"
57 selects the movable zone. "online_kernel" selects the
58 applicable kernel zone (DMA, DMA32, or Normal). However,
60 reading the file will return "online"; the zone information
77 For online memory blocks, it returns in which zone memory
82 For offline memory blocks, it returns by which zone memory
84 The first returned zone ("default") will be used when setting
|
| /Documentation/mm/ |
| D | balance.rst | 21 is, only when needed (aka zone free memory is 0), instead of making it
30 of incurring the overhead of regular zone balancing.
35 would not be done even when the dma zone was completely empty. 2.2 has
40 In 2.3, zone balancing can be done in one of two ways: depending on the
41 zone size (and possibly of the size of lower class zones), we can decide
43 zone. The good part is, while balancing, we do not need to look at sizes
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
58 Note that if the size of the regular zone is huge compared to dma zone,
60 deciding whether to balance the regular zone. The first solution
[all …]
|
| D | physical_memory.rst | 35 The memory range within a node that corresponds to a particular zone is
36 described by a ``struct zone``, typedeffed to ``zone_t``. Each zone has
45 Depending on the architecture, either of these zone types or even they both
52 the time. DMA operations can be performed on pages in this zone if the DMA
57 permanent mapping in the kernel page tables. The memory in this zone is only
58 accessible to the kernel using temporary mappings. This zone is available
72 It has different characteristics than RAM zone types and it exists to provide
78 ``ZONE_NORMAL`` so it is the most performance critical zone. Zones are
81 The relation between node and zone extents is determined by the physical memory
292 The highest zone index to be reclaimed by kswapd
[all …]
|
| D | numa.rst | 73 each memory zone [one or more of DMA, DMA32, NORMAL, HIGH_MEMORY, MOVABLE],
75 selected zone/node cannot satisfy the allocation request. This situation,
76 when a zone has no available memory to satisfy a request, is called
81 fall back to the same zone type on a different node, or to a different zone
92 nodes' zones in the selected zonelist looking for the first zone in the list
119 node the "local memory node"--the node of the first zone in CPU's node's
|
| /Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 13 The generic thermal sysfs provides a set of interfaces for thermal zone
17 This how-to focuses on enabling new thermal zone and cooling devices to
19 This solution is platform independent and any type of thermal zone devices
22 The main task of the thermal sysfs driver is to expose thermal zone attributes
25 inputs from thermal zone attributes (the current temperature and trip point
34 1.1 thermal zone device interface
48 This interface function adds a new thermal zone device (sensor) to the
53 the thermal zone type.
55 the table of trip points for this thermal zone.
59 thermal zone device call-backs.
[all …]
|
| D | power_allocator.rst | 12 point of the thermal zone.
17 thermal zone.
64 provided while registering the thermal zone. This estimates the
79 thermal-zone. For example::
88 Instead, if the thermal zone is registered from the platform code, pass a
195 thermal zone in which we are currently operating
214 thermal zone in which we are currently operating
257 If the thermal zone is registered using
259 are passed as part of the thermal zone's `thermal_bind_parameters`.
280 thermal zone should have power values reported either in milli-Watts
|
| D | x86_pkg_temperature_thermal.rst | 23 zone with maximum two user mode configurable trip points. Number of trip points
31 Each package will register as a thermal zone under /sys/class/thermal.
50 To get kobject-uevent notifications, set the thermal zone
|
| /Documentation/power/powercap/ |
| D | powercap.rst | 21 given zone belongs to. They each contain attributes for monitoring power, as
26 parent power zone containing multiple subzones and so on to reflect the power
28 capping to a set of devices together using the parent power zone and if more
161 In addition to that, each power zone contains a name attribute, allowing the
162 part of the system represented by that zone to be identified.
172 with different time windows to be applied to each power zone.
190 Power Zone Attributes
210 Name of this power zone.
242 Common zone and control type attributes
245 enabled (rw): Enable/Disable controls at zone level or for all zones using
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-zones.yaml | 8 title: Thermal zone
27 The polling-delay properties of a thermal-zone are bound to the maximum dT/dt
28 (temperature derivative over time) in two situations for a thermal zone:
30 2. when the zone just needs to be monitored (polling-delay) or when
58 Each thermal zone node contains information about how frequently it
60 this zone, one sub-node containing the various trip points for this
61 zone and one sub-node containing all the zone cooling-maps.
68 checking this thermal zone. Setting this to 0 disables the polling
70 sensors in this zone support interrupts.
76 checking this thermal zone while doing passive cooling. Setting
[all …]
|
| D | rcar-thermal.yaml | 20 - const: renesas,rcar-thermal # Generic without thermal-zone
26 - const: renesas,rcar-gen2-thermal # Generic thermal-zone
33 - const: renesas,rcar-gen2-thermal # Generic thermal-zone
34 - const: renesas,rcar-thermal # Generic without thermal-zone
120 # Example (with thermal-zone)
|
| /Documentation/admin-guide/sysctl/ |
| D | vm.rst | 314 debugfs shows what the fragmentation index for each order is in each zone in
319 The kernel will not compact memory in a zone if the
369 zone. This is because that memory could then be pinned via the mlock()
399 Each zone has an array of protection pages like this::
401 Node 0, zone DMA
415 These protections are added to score to judge whether this zone should be used
418 In this example, if normal pages (index=2) are required to this DMA zone and
419 watermark[WMARK_HIGH] is used for watermark, the kernel judges this zone should
421 (4 + 2004 = 2008). If this protection value is 0, this zone would be used for
422 normal page requirement. If requirement is DMA zone(index=0), protection[0]
[all …]
|
| /Documentation/hwmon/ |
| D | dme1737.rst | 188 be retrieved via the zone[1-3]_auto_channels_temp attributes. Each PWM output
189 is assigned to one (or hottest of multiple) temperature zone(s) through the
194 programmed via zone[1-3]_auto_point[1-3]_temp and
195 zone[1-3]_auto_point1_temp_hyst:
202 zone[1-3]_auto_point3_temp full-speed temp (all outputs)
203 zone[1-3]_auto_point2_temp full-speed temp
204 zone[1-3]_auto_point1_temp low-speed temp
205 zone[1-3]_auto_point1_temp_hyst min-speed temp
209 to auto_point2_pwm if the temperature of the associated zone is between
218 based on the temperature of the associated thermal zone:
[all …]
|
| D | asc7621.rst | 22 added PECI and a 4th thermal zone. The Andigilog aSC7611 is the
52 temperature may be mapped to any zone, which has a default assignment
55 Since there is a fan to zone assignment that allows for the "hotter" of
57 indication to the user, we have added an indicator that shows which zone
67 address. One could use our flexible zone assignment to have a zone
123 - Enhanced measured temperature to Temperature Zone assignment.
198 When the corresponding zone temperature reaches this value,
212 if the temperature for the zone is below the minimum.
214 temperature for the zone is below the minimum.
290 Temperature Zone 1, PECI is associated with
[all …]
|
| D | lm85.rst | 212 Each temperature sensor is associated with a Zone. There are three
213 sensors and therefore three zones (# 1, 2 and 3). Each zone has the following
230 configured and assigned to a zone for its control value. Each PWM can be
247 in this case actually affects all PWMs controlled by zone '#'.
249 PWM Controlling Zone selection
253 - controls zone that is associated with PWM
260 1 Controlled by Zone 1
261 2 Controlled by Zone 2
262 3 Controlled by Zone 3
263 23 Controlled by higher temp of Zone 2 or 3
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | repaper.txt | 21 - pervasive,thermal-zone: name of thermometer's thermal zone
51 pervasive,thermal-zone = "display";
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 166 The kernel will select the target zone automatically, depending on the
174 Or one can explicitly request a kernel zone (usually ZONE_NORMAL) by::
199 target zone automatically, depending on the configured ``online_policy``.
259 For an online memory block, the managing zone can be observed via::
341 When onlining, the zone is selected automatically.
357 zone for the memory block, such as ZONE_NORMAL.
358 ``online`` let's the kernel select the zone automatically.
363 ``valid_zones`` read-only: when a block is online, shows the zone it
364 belongs to; when a block is offline, shows what zone will
372 Other values indicate a kernel zone.
[all …]
|
1234