Lines Matching full:hierarchy
111 distribute system resources along the hierarchy in a controlled and
117 distributing a specific type of system resource along the hierarchy
132 sub-hierarchy of the cgroup. When a controller is enabled on a nested
134 restrictions set closer to the root in the hierarchy can not be
144 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
145 hierarchy can be mounted with the following mount command::
150 controllers which support v2 and are not bound to a v1 hierarchy are
151 automatically bound to the v2 hierarchy and show up at the root.
152 Controllers which are not in active use in the v2 hierarchy can be
153 bound to other hierarchies. This allows mixing v2 hierarchy with the
157 is no longer referenced in its current hierarchy. Because per-cgroup
160 the v2 hierarchy after the final umount of the previous hierarchy.
162 the unified hierarchy and it may take some time for the disabled
291 one for each hierarchy. The entry for cgroup v2 is always in the
322 cgroup whose resource domain is further up in the hierarchy. The root
416 "populated" field indicating whether the cgroup's sub-hierarchy has
421 sub-hierarchy have exited. The populated state updates and
422 notifications are recursive. Consider the following sub-hierarchy
459 Consider the following sub-hierarchy. The enabled controllers are
501 of the hierarchy which has it enabled, processes are always only on
545 delegated, the user can build sub-hierarchy under the directory,
549 happens in the delegated sub-hierarchy, nothing can escape the
553 cgroups in or nesting depth of a delegated sub-hierarchy; however,
560 A delegated sub-hierarchy is contained in the sense that processes
561 can't be moved into or out of the sub-hierarchy by the delegatee.
574 processes around freely in the delegated sub-hierarchy it can't pull
575 in from or push out to outside the sub-hierarchy.
583 ~ hierarchy ~
889 When delegating a sub-hierarchy, write access to this file
918 When delegating a sub-hierarchy, write access to this file
960 an attempt to create a new cgroup in the hierarchy will fail.
1048 each cgroup separately and aggregates it at each level of the hierarchy.
1050 deep level of the hierarchy, in which case this control attribute can
1382 hierarchy. For the local events at the cgroup level see
1772 implicitly disabled for child cgroups if the upper hierarchy
2101 The limits are only applied at the peer level in the hierarchy. This means that
2469 a partition root at the top of the hierarchy and its descendants
2482 proper "cpuset.cpus.exclusive" values down the cgroup hierarchy
2802 perf_event controller, if not mounted on a legacy hierarchy, is
2803 automatically enabled on the v2 hierarchy so that perf events can
2805 moved to a legacy hierarchy after v2 hierarchy is populated.
2879 the threads). This is natural for the v2 hierarchy; however, for the
2944 /batchjobs/container_id1, and assuming that the global hierarchy is
2954 namespace should only be exposed to its own cgroupns hierarchy.
2970 Namespace specific cgroup hierarchy can be mounted by a process
2975 This will mount the unified cgroup hierarchy with cgroupns root as the
2980 the view of cgroup hierarchy by namespace-private cgroupfs mount
3049 hierarchy could host any number of controllers. While this seemed to
3055 the fact that controllers couldn't be moved to another hierarchy once
3057 bound to a hierarchy were forced to have exactly the same view of the
3058 hierarchy. It wasn't possible to vary the granularity depending on
3062 put on the same hierarchy and most configurations resorted to putting
3063 each controller on its own hierarchy. Only closely related ones, such
3065 hierarchy. This often meant that userland ended up managing multiple
3066 similar hierarchies repeating the same steps on each hierarchy
3067 whenever a hierarchy management operation was necessary.
3091 depending on the specific controller. In other words, hierarchy may
3121 extract the path on the target hierarchy from /proc/self/cgroup,
3126 that the process would actually be operating on its own sub-hierarchy.
3226 in the hierarchy. This makes subtree delegation impossible. Second,
3287 and that's why unified hierarchy allows distributing it separately.