Lines Matching refs:which

38 type controllers such as freezer which can be useful in all
45 In practice, these issues heavily limit which controllers can be put
58 There's no limit on how many hierarchies there may be, which means
61 length, which makes it highly awkward to handle and leads to addition
62 of controllers which exist only to identify membership, which in turn
71 In most use cases, putting controllers on hierarchies which are
97 All controllers which support the unified hierarchy and are not bound
99 show up at the root of it.  Controllers which are enabled only in the
131 which governs which controllers are enabled on the children of the
137 root's "cgroup.subtree_control" file determines which controllers are
159 controllers which can be enabled in the cgroup's
162 In the root cgroup, this lists controllers which are not bound to
177 controllers which are enabled in the parent's "cgroup.subtree_control"
197 universal, and there are various other knobs which simply aren't
204 extra layer of nesting which may not be necessary, makes the interface
211 this direction will lead to problems which will be extremely difficult
219 It is clear that this is something which needs to be addressed from
225  Except for the root, only cgroups which don't contain any task may
229 controller is looking at the part of the hierarchy which has it
236 consumption which can't be associated with any other cgroup and
276 which can be used to monitor whether the cgroup's subhierarchy has
346   ancestors are below their low boundaries, which makes delegation of
414 Unified hierarchy will require one of the capabilities(7), which is
419 "cgroup.procs" interface file; however, all operations which affect
425 binaries.  cgroup exposes various aspects of the system in ways which
436 useful features which may not be suitable for general consumption in a
441 details in a way which can exert significant pain by locking the