Searched full:hierarchy (Results 1 – 25 of 126) sorted by relevance
123456
| /Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 153 HIERARCHY = NONE
181 HIERARCHY = NONE
196 HIERARCHY = NONE
211 HIERARCHY = NONE
226 HIERARCHY = NONE
241 HIERARCHY = NONE
256 HIERARCHY = NONE
271 HIERARCHY = NONE
286 HIERARCHY = NONE
301 HIERARCHY = NONE
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 60 A *hierarchy* is a set of cgroups arranged in a tree, such that
62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy. Each hierarchy has
67 cgroups. Each hierarchy is a partition of all tasks in the system.
72 a cgroup. Those creations and assignments only affect the hierarchy
101 Multiple hierarchy support is provided to allow for situations where
104 hierarchy to be a natural division of tasks, without having to handle
110 separate hierarchy; at the other extreme, all subsystems
111 would be attached to the same hierarchy.
149 With only a single hierarchy, he now would potentially have to create
[all …]
|
| D | pids.rst | 8 The process number controller is used to allow a cgroup hierarchy to stop any
13 preventable in the scope of a cgroup hierarchy by allowing resource limiting of
32 limit in the hierarchy is followed).
49 Then we create a hierarchy, set limits and attach processes to it::
68 not be able to overcome the most stringent limit in the hierarchy (in this case,
|
| D | devices.rst | 57 4. Hierarchy
60 device cgroups maintain hierarchy by making sure a cgroup never has more
123 4.1 Hierarchy (internal implementation)
130 to devices will be propagated down the hierarchy.
|
| D | blkio-controller.rst | 9 both at leaf nodes as well as at intermediate nodes in a storage hierarchy.
55 Throttling implements hierarchy support; however,
56 throttling's hierarchy support is enabled iff "sane_behavior" is
60 If somebody created a hierarchy like as follows::
69 hierarchy correctly. For throttling, all limits apply
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 215 Hierarchy IRQ domain
232 interrupt controller and those irq_domains are organized into hierarchy.
233 When building irq_domain hierarchy, the irq_domain near to the device is
234 child and the irq_domain near to CPU is parent. So a hierarchy structure
245 There are four major interfaces to use hierarchy irq_domain:
256 Following changes are needed to support hierarchy irq_domain:
259 maintain irq_domain hierarchy information.
261 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
263 3) new callbacks are added to struct irq_domain_ops to support hierarchy
266 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /Documentation/mm/ |
| D | page_tables.rst | 16 Linux defines page tables as a hierarchy which is currently five levels in
38 Over time a deeper hierarchy has been developed in response to increasing memory
44 The software page table hierarchy reflects the fact that page table hardware has
53 to mark large areas as unmapped at a higher level in the page table hierarchy.
59 traverse deeper in the hierarchy when you find a large mapped range like this.
61 The page table hierarchy has now developed into this::
84 Symbols on the different levels of the page table hierarchy have the following
102 - **pmd**, `pmd_t`, `pmdval_t` = **Page Middle Directory**, the hierarchy right
124 To repeat: each level in the page table hierarchy is a *array of pointers*, so
|
| /Documentation/userspace-api/ |
| D | landlock.rst | 32 file hierarchy, and the related filesystem actions are defined with `access
111 file hierarchy ``/usr``. Without another rule, write actions would then be
182 It is recommended setting access rights to file hierarchy leaves as much as
184 read-only hierarchy and ``~/tmp/`` as a read-write hierarchy, compared to
185 ``~/`` as a read-only hierarchy and ``~/tmp/`` as a read-write hierarchy.
224 A bind mount mirrors a source file hierarchy to a destination. The destination
225 hierarchy is then composed of the exact same files, on which Landlock rules can
232 combined in a merge directory, result of the mount point. This merge hierarchy
234 on the merge hierarchy only reflects on the upper layer. From a Landlock
238 restrict the resulted merged hierarchy, and vice versa. Landlock users should
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.yaml | 36 This node contains a hierarchy of PM domain nodes, which should match the
37 Power Area Hierarchy in the Power Domain Specifications section of the
90 // This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | prcm.txt | 4 a DT hierarchy. Each TI SoC can have multiple PRCM entities listed for it,
5 each describing one module and the clock hierarchy under it. see [1] for
|
| D | prm-inst.txt | 6 hierarchy.
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
20 cache hierarchy is also out of standby, and then the cpu is allowed to resume
39 system state including cache hierarchy is ready before allowing core to
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 13 transactions between hierarchy domains, and in PCIe, each Root Port
14 defines a separate hierarchy domain. To make things worse, there is no
18 same PCI bridge, as such devices are all in the same PCI hierarchy
20 hierarchy will be routable, but it does not require routing
|
| /Documentation/admin-guide/ |
| D | cgroup-v2.rst | 110 distribute system resources along the hierarchy in a controlled and
116 distributing a specific type of system resource along the hierarchy
131 sub-hierarchy of the cgroup. When a controller is enabled on a nested
133 restrictions set closer to the root in the hierarchy can not be
143 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
144 hierarchy can be mounted with the following mount command::
149 controllers which support v2 and are not bound to a v1 hierarchy are
150 automatically bound to the v2 hierarchy and show up at the root.
151 Controllers which are not in active use in the v2 hierarchy can be
152 bound to other hierarchies. This allows mixing v2 hierarchy with the
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | ti,omap-gpio.yaml | 61 SoCs which have not been converted to the ti,sysc interconnect hierarchy.
68 have not been converted to the ti,sysc interconnect hierarchy.
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 71 node sysfs hierarchy by appending the attributes directory under the
102 System memory may be constructed in a hierarchy of elements with various
106 by the last memory level in the hierarchy. The system meanwhile uses
111 hierarchy. Each increasing cache level provides higher performing
|
| /Documentation/PCI/ |
| D | pcieaer-howto.rst | 133 hierarchy and links. These errors do not include any device specific
156 with downstream device drivers associated with a hierarchy in question
182 pci_channel_io_normal) to all drivers associated within a hierarchy in
187 If Upstream Port A captures an AER error, the hierarchy consists of
196 a hierarchy in question. Then, performing link reset at upstream is
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-memory-tiers | 22 hierarchy.
|
| D | sysfs-firmware-papr-energy-scale-info | 8 attribute hierarchy pertaining to performance/
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 9 In a SMP system, the hierarchy of CPUs is defined through three entities that
17 The bottom hierarchy level sits at core or thread level depending on whether
21 threads existing in the system and map to the hierarchy level "thread" above.
23 in the system and map to the hierarchy level "core" above.
26 corresponding to the system hierarchy; syntactically they are defined as device
33 correspond to physical CPUs and are to be mapped to the hierarchy levels.
92 levels) since name uniqueness will be guaranteed by the device tree hierarchy.
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 11 hardware hierarchy.
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 64 the device's directory in the physical hierarchy.
67 to the device's directory in the physical hierarchy.
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 82 2. Otherwise, the cpuset hierarchy of the task is walked until an
94 policy or cpuset hierarchy, in which case the ``execve(2)`` continues
136 (2) of the process described in `execve(2)`_ and the cpuset hierarchy is
|
| /Documentation/filesystems/ |
| D | configfs.rst | 328 the item hierarchy. If a client needs to do some cleanup before this
375 Hierarchy Navigation and the Subsystem Mutex
379 config_items are arranged in a hierarchy due to the fact that they
381 parts, but the subsystem might be interested in this hierarchy. For
382 this reason, the hierarchy is mirrored via the config_group->cg_children
387 management of the hierarchy, so configfs uses the subsystem mutex to
389 hierarchy, it must do so under the protection of the subsystem
393 allocated item has not been linked into this hierarchy. Similarly, it
|
| /Documentation/arch/loongarch/ |
| D | irq-chip-model.rst | 4 IRQ chip model (hierarchy) of LoongArch
16 in chipsets). These controllers (in other words, irqchips) are linked in a hierarchy,
17 and there are two models of hierarchy (legacy model and extended model).
|
123456