Lines Matching refs:hierarchy
105 distribute system resources along the hierarchy in a controlled and
111 distributing a specific type of system resource along the hierarchy
126 sub-hierarchy of the cgroup. When a controller is enabled on a nested
128 restrictions set closer to the root in the hierarchy can not be
138 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
139 hierarchy can be mounted with the following mount command::
144 controllers which support v2 and are not bound to a v1 hierarchy are
145 automatically bound to the v2 hierarchy and show up at the root.
146 Controllers which are not in active use in the v2 hierarchy can be
147 bound to other hierarchies. This allows mixing v2 hierarchy with the
151 is no longer referenced in its current hierarchy. Because per-cgroup
154 the v2 hierarchy after the final umount of the previous hierarchy.
156 the unified hierarchy and it may take some time for the disabled
244 one for each hierarchy. The entry for cgroup v2 is always in the
275 cgroup whose resource domain is further up in the hierarchy. The root
362 "populated" field indicating whether the cgroup's sub-hierarchy has
367 sub-hierarchy have exited. The populated state updates and
368 notifications are recursive. Consider the following sub-hierarchy
405 Consider the following sub-hierarchy. The enabled controllers are
447 of the hierarchy which has it enabled, processes are always only on
489 delegated, the user can build sub-hierarchy under the directory,
493 happens in the delegated sub-hierarchy, nothing can escape the
497 cgroups in or nesting depth of a delegated sub-hierarchy; however,
504 A delegated sub-hierarchy is contained in the sense that processes
505 can't be moved into or out of the sub-hierarchy by the delegatee.
518 processes around freely in the delegated sub-hierarchy it can't pull
519 in from or push out to outside the sub-hierarchy.
527 ~ hierarchy ~
831 When delegating a sub-hierarchy, write access to this file
860 When delegating a sub-hierarchy, write access to this file
902 an attempt to create a new cgroup in the hierarchy will fail.
1211 hierarchy. For for the local events at the cgroup level see
1781 The limits are only applied at the peer level in the hierarchy. This means that
2213 perf_event controller, if not mounted on a legacy hierarchy, is
2214 automatically enabled on the v2 hierarchy so that perf events can
2216 moved to a legacy hierarchy after v2 hierarchy is populated.
2290 the threads). This is natural for the v2 hierarchy; however, for the
2355 /batchjobs/container_id1, and assuming that the global hierarchy is
2365 namespace should only be exposed to its own cgroupns hierarchy.
2381 Namespace specific cgroup hierarchy can be mounted by a process
2386 This will mount the unified cgroup hierarchy with cgroupns root as the
2391 the view of cgroup hierarchy by namespace-private cgroupfs mount
2460 hierarchy could host any number of controllers. While this seemed to
2466 the fact that controllers couldn't be moved to another hierarchy once
2468 bound to a hierarchy were forced to have exactly the same view of the
2469 hierarchy. It wasn't possible to vary the granularity depending on
2473 put on the same hierarchy and most configurations resorted to putting
2474 each controller on its own hierarchy. Only closely related ones, such
2476 hierarchy. This often meant that userland ended up managing multiple
2477 similar hierarchies repeating the same steps on each hierarchy
2478 whenever a hierarchy management operation was necessary.
2502 depending on the specific controller. In other words, hierarchy may
2532 extract the path on the target hierarchy from /proc/self/cgroup,
2537 that the process would actually be operating on its own sub-hierarchy.
2637 in the hierarchy. This makes subtree delegation impossible. Second,
2698 and that's why unified hierarchy allows distributing it separately.