Lines Matching full:hierarchy
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
156 is no longer referenced in its current hierarchy. Because per-cgroup
159 the v2 hierarchy after the final umount of the previous hierarchy.
161 the unified hierarchy and it may take some time for the disabled
283 one for each hierarchy. The entry for cgroup v2 is always in the
314 cgroup whose resource domain is further up in the hierarchy. The root
408 "populated" field indicating whether the cgroup's sub-hierarchy has
413 sub-hierarchy have exited. The populated state updates and
414 notifications are recursive. Consider the following sub-hierarchy
451 Consider the following sub-hierarchy. The enabled controllers are
493 of the hierarchy which has it enabled, processes are always only on
535 delegated, the user can build sub-hierarchy under the directory,
539 happens in the delegated sub-hierarchy, nothing can escape the
543 cgroups in or nesting depth of a delegated sub-hierarchy; however,
550 A delegated sub-hierarchy is contained in the sense that processes
551 can't be moved into or out of the sub-hierarchy by the delegatee.
564 processes around freely in the delegated sub-hierarchy it can't pull
565 in from or push out to outside the sub-hierarchy.
573 ~ hierarchy ~
879 When delegating a sub-hierarchy, write access to this file
908 When delegating a sub-hierarchy, write access to this file
950 an attempt to create a new cgroup in the hierarchy will fail.
1030 each cgroup separately and aggregates it at each level of the hierarchy.
1032 deep level of the hierarchy, in which case this control attribute can
1354 hierarchy. For the local events at the cgroup level see
2025 The limits are only applied at the peer level in the hierarchy. This means that
2369 a partition root at the top of the hierarchy and its descendants
2382 proper "cpuset.cpus.exclusive" values down the cgroup hierarchy
2645 perf_event controller, if not mounted on a legacy hierarchy, is
2646 automatically enabled on the v2 hierarchy so that perf events can
2648 moved to a legacy hierarchy after v2 hierarchy is populated.
2722 the threads). This is natural for the v2 hierarchy; however, for the
2787 /batchjobs/container_id1, and assuming that the global hierarchy is
2797 namespace should only be exposed to its own cgroupns hierarchy.
2813 Namespace specific cgroup hierarchy can be mounted by a process
2818 This will mount the unified cgroup hierarchy with cgroupns root as the
2823 the view of cgroup hierarchy by namespace-private cgroupfs mount
2892 hierarchy could host any number of controllers. While this seemed to
2898 the fact that controllers couldn't be moved to another hierarchy once
2900 bound to a hierarchy were forced to have exactly the same view of the
2901 hierarchy. It wasn't possible to vary the granularity depending on
2905 put on the same hierarchy and most configurations resorted to putting
2906 each controller on its own hierarchy. Only closely related ones, such
2908 hierarchy. This often meant that userland ended up managing multiple
2909 similar hierarchies repeating the same steps on each hierarchy
2910 whenever a hierarchy management operation was necessary.
2934 depending on the specific controller. In other words, hierarchy may
2964 extract the path on the target hierarchy from /proc/self/cgroup,
2969 that the process would actually be operating on its own sub-hierarchy.
3069 in the hierarchy. This makes subtree delegation impossible. Second,
3130 and that's why unified hierarchy allows distributing it separately.