Lines Matching refs:controllers

16   2-3. cgroup.controllers
40 can host any number of controllers.  While this seems to provide a
44 type controllers such as freezer which can be useful in all
46 fact that controllers can't be moved around once hierarchies are
47 populated.  Another issue is that all controllers bound to a hierarchy
51 In practice, these issues heavily limit which controllers can be put
54 the cpu and cpuacct controllers, make sense to put on the same
62 restricts how cgroup is used in general and what controllers can do.
68 of controllers which exist only to identify membership, which in turn
72 of hierarchies other controllers would be on, each controller has to
73 assume that all other controllers are operating on completely
75 cumbersome, for controllers to cooperate with each other.
77 In most use cases, putting controllers on hierarchies which are
82 controllers.  For example, a given configuration might not care about
103 All controllers which support the unified hierarchy and are not bound
112 controller states are destroyed asynchronously and controllers may
118 furthermore, due to dependencies among controllers, other controllers
122 moving controllers between the unified and other hierarchies is
125 controllers.
131 which governs which controllers are enabled on the children of the
137 root's "cgroup.subtree_control" file determines which controllers are
139 fact that controllers on the immediate sub-level are used to
148 enabled controllers.  A write to the file should contain a
149 space-separated list of controllers with '+' or '-' prefixed (without
156 2-3. cgroup.controllers
158 Read-only "cgroup.controllers" file contains a space-separated list of
159 controllers which can be enabled in the cgroup's
162 In the root cgroup, this lists controllers which are not bound to
163 other hierarchies and the content changes as controllers are bound to
167 parent's "cgroup.subtree_control" file as only controllers enabled
177 controllers which are enabled in the parent's "cgroup.subtree_control"
189 controllers are doing different things.
214 Multiple controllers struggle with internal tasks and came up with
220 cgroup core proper in a uniform way so that controllers don't need to
226  have controllers enabled in their "cgroup.subtree_control" files.
237 requires special treatment from most controllers.  How resource
245 before enabling controllers in its "cgroup.subtree_control" file.
261 controllers are hierarchical and regardless of what happens in the
400 reading; however, controllers may allow omitting later fields or
447   new name is more in line with the other two major controllers, cpu
631 Also, due to the specific nature, cgroup and its controllers don't