Lines Matching refs:hierarchy
102 distribute system resources along the hierarchy in a controlled and
108 distributing a specific type of system resource along the hierarchy
123 sub-hierarchy of the cgroup. When a controller is enabled on a nested
125 restrictions set closer to the root in the hierarchy can not be
135 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
136 hierarchy can be mounted with the following mount command::
141 controllers which support v2 and are not bound to a v1 hierarchy are
142 automatically bound to the v2 hierarchy and show up at the root.
143 Controllers which are not in active use in the v2 hierarchy can be
144 bound to other hierarchies. This allows mixing v2 hierarchy with the
148 is no longer referenced in its current hierarchy. Because per-cgroup
151 the v2 hierarchy after the final umount of the previous hierarchy.
153 the unified hierarchy and it may take some time for the disabled
230 one for each hierarchy. The entry for cgroup v2 is always in the
261 cgroup whose resource domain is further up in the hierarchy. The root
348 "populated" field indicating whether the cgroup's sub-hierarchy has
353 sub-hierarchy have exited. The populated state updates and
354 notifications are recursive. Consider the following sub-hierarchy
391 Consider the following sub-hierarchy. The enabled controllers are
433 of the hierarchy which has it enabled, processes are always only on
475 delegated, the user can build sub-hierarchy under the directory,
479 happens in the delegated sub-hierarchy, nothing can escape the
483 cgroups in or nesting depth of a delegated sub-hierarchy; however,
490 A delegated sub-hierarchy is contained in the sense that processes
491 can't be moved into or out of the sub-hierarchy by the delegatee.
504 processes around freely in the delegated sub-hierarchy it can't pull
505 in from or push out to outside the sub-hierarchy.
513 ~ hierarchy ~
819 When delegating a sub-hierarchy, write access to this file
848 When delegating a sub-hierarchy, write access to this file
890 an attempt to create a new cgroup in the hierarchy will fail.
1191 hierarchy. For for the local events at the cgroup level see
1709 The limits are only applied at the peer level in the hierarchy. This means that
2060 perf_event controller, if not mounted on a legacy hierarchy, is
2061 automatically enabled on the v2 hierarchy so that perf events can
2063 moved to a legacy hierarchy after v2 hierarchy is populated.
2137 the threads). This is natural for the v2 hierarchy; however, for the
2202 /batchjobs/container_id1, and assuming that the global hierarchy is
2212 namespace should only be exposed to its own cgroupns hierarchy.
2228 Namespace specific cgroup hierarchy can be mounted by a process
2233 This will mount the unified cgroup hierarchy with cgroupns root as the
2238 the view of cgroup hierarchy by namespace-private cgroupfs mount
2307 hierarchy could host any number of controllers. While this seemed to
2313 the fact that controllers couldn't be moved to another hierarchy once
2315 bound to a hierarchy were forced to have exactly the same view of the
2316 hierarchy. It wasn't possible to vary the granularity depending on
2320 put on the same hierarchy and most configurations resorted to putting
2321 each controller on its own hierarchy. Only closely related ones, such
2323 hierarchy. This often meant that userland ended up managing multiple
2324 similar hierarchies repeating the same steps on each hierarchy
2325 whenever a hierarchy management operation was necessary.
2349 depending on the specific controller. In other words, hierarchy may
2379 extract the path on the target hierarchy from /proc/self/cgroup,
2384 that the process would actually be operating on its own sub-hierarchy.
2484 in the hierarchy. This makes subtree delegation impossible. Second,
2545 and that's why unified hierarchy allows distributing it separately.