Lines Matching full:controllers
25 2-4. Controlling Controllers
44 5. Controllers
97 qualifier as in "cgroup controllers". When explicitly referring to
108 cgroup is largely composed of two parts - the core and controllers.
112 although there are utility controllers which serve purposes other than
122 Following certain structural constraints, controllers may be enabled or
144 controllers which support v2 and are not bound to a v1 hierarchy are
146 Controllers which are not in active use in the v2 hierarchy can be
152 controller states are destroyed asynchronously and controllers may
158 to inter-controller dependencies, other controllers may need to be
162 controllers dynamically between the v2 and other hierarchies is
165 controllers after system boot.
168 automount the v1 cgroup filesystem and so hijack all controllers
171 disabling controllers in v1 and make them always available in v2.
262 cgroup v2 supports thread granularity for a subset of controllers to
270 Controllers which support thread mode are called threaded controllers.
271 The ones which don't are called domain controllers.
282 constraint - threaded controllers can be enabled on non-leaf cgroups
310 controllers enabled or populated domain children. The root is
325 cgroup becomes threaded or threaded controllers are enabled in the
346 Only threaded controllers can be enabled in a threaded subtree. When
381 Controlling Controllers
387 Each cgroup has a "cgroup.controllers" file which lists all
388 controllers available for the cgroup to enable::
390 # cat cgroup.controllers
393 No controller is enabled by default. Controllers can be enabled and
398 Only controllers which are listed in "cgroup.controllers" can be
405 Consider the following sub-hierarchy. The enabled controllers are
432 can only contain controllers which are enabled in the parent's
444 controllers enabled in their "cgroup.subtree_control" files.
454 controllers. How resource consumption in the root cgroup is governed
456 refer to the Non-normative information section in the Controllers
464 children before enabling controllers in its "cgroup.subtree_control"
492 of all resource controllers are hierarchical and regardless of what
585 cgroup controllers implement several resource distribution schemes
704 reading; however, controllers may allow omitting later fields or
803 It can't be populated or have controllers enabled. It may
863 cgroup.controllers
867 It shows space separated list of all controllers available to
868 the cgroup. The controllers are not ordered.
874 When read, it shows space separated list of the controllers
878 Space separated list of controllers prefixed with '+' or '-'
879 can be written to enable or disable controllers. A controller
955 Controllers chapter
961 The "cpu" controllers regulates distribution of CPU cycles. This
1830 This takes a similar format as the other controllers.
1914 controllers cannot prevent, thus warranting its own controller. For
2400 controllers are not covered.
2449 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2460 hierarchy could host any number of controllers. While this seemed to
2464 type controllers such as freezer which can be useful in all
2466 the fact that controllers couldn't be moved to another hierarchy once
2467 hierarchies were populated. Another issue was that all controllers
2472 In practice, these issues heavily limited which controllers could be
2475 as the cpu and cpuacct controllers, made sense to be put on the same
2483 used in general and what controllers was able to do.
2489 addition of controllers which existed only to identify membership,
2494 topologies of hierarchies other controllers might be on, each
2495 controller had to assume that all other controllers were attached to
2497 least very cumbersome, for controllers to cooperate with each other.
2499 In most use cases, putting controllers on hierarchies which are
2504 controllers. For example, a given configuration might not care about
2513 This didn't make sense for some controllers and those controllers
2539 cgroup controllers implemented a number of knobs which would never be
2560 settle it. Different controllers did different things.
2585 Multiple controllers struggled with internal tasks and came up with
2606 controllers completely ignoring hierarchical organization and treating
2608 cgroup. Some controllers exposed a large amount of inconsistent
2611 There also was no consistency across controllers. When a new cgroup
2612 was created, some controllers defaulted to not imposing extra
2620 controllers so that they expose minimal and consistent interfaces.
2696 that cgroup controllers should account and limit specific physical