Lines Matching refs:hierarchy

2 Cgroup unified hierarchy
6 This document describes the changes made by unified hierarchy and
39 cgroup allows an arbitrary number of hierarchies and each hierarchy
47 populated.  Another issue is that all controllers bound to a hierarchy
48 are forced to have exactly the same view of the hierarchy.  It isn't
52 on the same hierarchy and most configurations resort to putting each
53 controller on its own hierarchy.  Only closely related ones, such as
55 hierarchy.  This often means that userland ends up managing multiple
56 similar hierarchies repeating the same steps on each hierarchy
57 whenever a hierarchy management operation is necessary.
80 depending on the specific controller.  In other words, hierarchy may
86 Unified hierarchy is the next version of cgroup interface.  It aims to
97 Currently, unified hierarchy can be mounted with the following mount
103 All controllers which support the unified hierarchy and are not bound
104 to other hierarchies are automatically bound to unified hierarchy and
106 root of unified hierarchy can be bound to other hierarchies.  This
107 allows mixing unified hierarchy with the traditional multiple
111 is no longer referenced in its current hierarchy.  Because per-cgroup
114 the unified hierarchy after the final umount of the previous
115 hierarchy.  Similarly, a controller should be fully disabled to be
116 moved out of the unified hierarchy and it may take some time for the
130 All cgroups on unified hierarchy have a "cgroup.subtree_control" file
132 cgroup.  Let's assume a hierarchy like the following.
222 behavior.  To achieve that, unified hierarchy enforces the following
229 controller is looking at the part of the hierarchy which has it
258 Once delegated, the user can build sub-hierarchy under the directory,
262 delegated sub-hierarchy, nothing can escape the resource restrictions
266 cgroups in or nesting depth of a delegated sub-hierarchy; however,
272 On the unified hierarchy, to write to a "cgroup.procs" file, in
283  ~ hierarchy ~
287 regardless of their relative positions in the hierarchy.  The
297 only be able to move processes in each sub-hierarchy but also across
302 On the unified hierarchy, let's say U0 wants to write the pid of a
338 Unified hierarchy implements "populated" field in "cgroup.events"
350 In unified hierarchy, the release_agent mechanism is no longer
524   are located in the hierarchy.  This makes subtree delegation
600 Unified hierarchy will require one of the capabilities(7), which is