Lines Matching full:controllers
25 2-4. Controlling Controllers
44 5. Controllers
94 qualifier as in "cgroup controllers". When explicitly referring to
105 cgroup is largely composed of two parts - the core and controllers.
109 although there are utility controllers which serve purposes other than
119 Following certain structural constraints, controllers may be enabled or
141 controllers which support v2 and are not bound to a v1 hierarchy are
143 Controllers which are not in active use in the v2 hierarchy can be
149 controller states are destroyed asynchronously and controllers may
155 to inter-controller dependencies, other controllers may need to be
159 controllers dynamically between the v2 and other hierarchies is
162 controllers after system boot.
165 automount the v1 cgroup filesystem and so hijack all controllers
168 disabling controllers in v1 and make them always available in v2.
248 cgroup v2 supports thread granularity for a subset of controllers to
256 Controllers which support thread mode are called threaded controllers.
257 The ones which don't are called domain controllers.
268 constraint - threaded controllers can be enabled on non-leaf cgroups
296 controllers enabled or populated domain children. The root is
311 cgroup becomes threaded or threaded controllers are enabled in the
332 Only threaded controllers can be enabled in a threaded subtree. When
367 Controlling Controllers
373 Each cgroup has a "cgroup.controllers" file which lists all
374 controllers available for the cgroup to enable::
376 # cat cgroup.controllers
379 No controller is enabled by default. Controllers can be enabled and
384 Only controllers which are listed in "cgroup.controllers" can be
391 Consider the following sub-hierarchy. The enabled controllers are
418 can only contain controllers which are enabled in the parent's
430 controllers enabled in their "cgroup.subtree_control" files.
440 controllers. How resource consumption in the root cgroup is governed
442 refer to the Non-normative information section in the Controllers
450 children before enabling controllers in its "cgroup.subtree_control"
478 of all resource controllers are hierarchical and regardless of what
571 cgroup controllers implement several resource distribution schemes
690 reading; however, controllers may allow omitting later fields or
791 It can't be populated or have controllers enabled. It may
851 cgroup.controllers
855 It shows space separated list of all controllers available to
856 the cgroup. The controllers are not ordered.
862 When read, it shows space separated list of the controllers
866 Space separated list of controllers prefixed with '+' or '-'
867 can be written to enable or disable controllers. A controller
943 Controllers chapter
949 The "cpu" controllers regulates distribution of CPU cycles. This
1758 This takes a similar format as the other controllers.
1788 controllers cannot prevent, thus warranting its own controller. For
2247 controllers are not covered.
2296 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2307 hierarchy could host any number of controllers. While this seemed to
2311 type controllers such as freezer which can be useful in all
2313 the fact that controllers couldn't be moved to another hierarchy once
2314 hierarchies were populated. Another issue was that all controllers
2319 In practice, these issues heavily limited which controllers could be
2322 as the cpu and cpuacct controllers, made sense to be put on the same
2330 used in general and what controllers was able to do.
2336 addition of controllers which existed only to identify membership,
2341 topologies of hierarchies other controllers might be on, each
2342 controller had to assume that all other controllers were attached to
2344 least very cumbersome, for controllers to cooperate with each other.
2346 In most use cases, putting controllers on hierarchies which are
2351 controllers. For example, a given configuration might not care about
2360 This didn't make sense for some controllers and those controllers
2386 cgroup controllers implemented a number of knobs which would never be
2407 settle it. Different controllers did different things.
2432 Multiple controllers struggled with internal tasks and came up with
2453 controllers completely ignoring hierarchical organization and treating
2455 cgroup. Some controllers exposed a large amount of inconsistent
2458 There also was no consistency across controllers. When a new cgroup
2459 was created, some controllers defaulted to not imposing extra
2467 controllers so that they expose minimal and consistent interfaces.
2543 that cgroup controllers should account and limit specific physical