Lines Matching full:hierarchy

60 A *hierarchy* is a set of cgroups arranged in a tree, such that
62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy.  Each hierarchy has
67 cgroups. Each hierarchy is a partition of all tasks in the system.
72 a cgroup. Those creations and assignments only affect the hierarchy
99 Multiple hierarchy support is provided to allow for situations where
102 hierarchy to be a natural division of tasks, without having to handle
108 separate hierarchy; at the other extreme, all subsystems
109 would be attached to the same hierarchy.
147 With only a single hierarchy, he now would potentially have to create
181    the cgroup of which it's a member in each hierarchy, but this
191  - A cgroup hierarchy filesystem can be mounted for browsing and
206 kernel.  When mounting a cgroup hierarchy, you may specify a
209 mount a hierarchy containing all registered subsystems.
211 If an active hierarchy with exactly the same set of subsystems already
212 exists, it will be reused for the new mount. If no existing hierarchy
214 hierarchy, the mount will fail with -EBUSY. Otherwise, a new hierarchy
218 cgroup hierarchy, or to unbind a subsystem from an active cgroup
219 hierarchy. This may be possible in future, but is fraught with nasty
223 child cgroups created below the top-level cgroup, that hierarchy
225 child cgroups then the hierarchy will be deactivated.
231 for each active hierarchy, the subsystem names and the cgroup name
283 cgroup hierarchy provides for a familiar permission and name space
293 of the "release_agent" file in that hierarchy's root directory,
300 a cgroup hierarchy's release_agent path is empty.
352 To mount a cgroup hierarchy with all available subsystems, type::
372 To mount a cgroup hierarchy with just the cpuset and memory
380 hierarchy is empty and release_agent itself should be replaced with
384 To Specify a hierarchy's release_agent::
392 when the hierarchy consists of a single (root) cgroup. Supporting
394 cgroup hierarchy is intended to be implemented in the future.
464 mounted hierarchy, to remove a task from its current cgroup you must
474 Passing the name=<x> option when mounting a cgroups hierarchy
475 associates the given name with the hierarchy.  This can be used when
476 mounting a pre-existing hierarchy, in order to refer to it by name
477 rather than by its set of active subsystems.  Each hierarchy is either
482 When passing a name=<x> option for a new hierarchy, you need to
487 The name of the subsystem appears as part of the hierarchy description
560 it's the root of the hierarchy) and may be an appropriate place for
570 propagation along the hierarchy. See the comment on
617 initial state.  This is currently only used on the unified hierarchy
658 Called when a cgroup subsystem is rebound to a different hierarchy
660 the default hierarchy (which never has sub-cgroups) and a hierarchy