Lines Matching full:controllers
25 2-4. Controlling Controllers
44 5. Controllers
96 qualifier as in "cgroup controllers". When explicitly referring to
107 cgroup is largely composed of two parts - the core and controllers.
111 although there are utility controllers which serve purposes other than
121 Following certain structural constraints, controllers may be enabled or
143 controllers which support v2 and are not bound to a v1 hierarchy are
145 Controllers which are not in active use in the v2 hierarchy can be
151 controller states are destroyed asynchronously and controllers may
157 to inter-controller dependencies, other controllers may need to be
161 controllers dynamically between the v2 and other hierarchies is
164 controllers after system boot.
167 automount the v1 cgroup filesystem and so hijack all controllers
170 disabling controllers in v1 and make them always available in v2.
261 cgroup v2 supports thread granularity for a subset of controllers to
269 Controllers which support thread mode are called threaded controllers.
270 The ones which don't are called domain controllers.
281 constraint - threaded controllers can be enabled on non-leaf cgroups
309 controllers enabled or populated domain children. The root is
324 cgroup becomes threaded or threaded controllers are enabled in the
345 Only threaded controllers can be enabled in a threaded subtree. When
380 Controlling Controllers
386 Each cgroup has a "cgroup.controllers" file which lists all
387 controllers available for the cgroup to enable::
389 # cat cgroup.controllers
392 No controller is enabled by default. Controllers can be enabled and
397 Only controllers which are listed in "cgroup.controllers" can be
404 Consider the following sub-hierarchy. The enabled controllers are
431 can only contain controllers which are enabled in the parent's
443 controllers enabled in their "cgroup.subtree_control" files.
453 controllers. How resource consumption in the root cgroup is governed
455 refer to the Non-normative information section in the Controllers
463 children before enabling controllers in its "cgroup.subtree_control"
491 of all resource controllers are hierarchical and regardless of what
584 cgroup controllers implement several resource distribution schemes
703 reading; however, controllers may allow omitting later fields or
802 It can't be populated or have controllers enabled. It may
862 cgroup.controllers
866 It shows space separated list of all controllers available to
867 the cgroup. The controllers are not ordered.
873 When read, it shows space separated list of the controllers
877 Space separated list of controllers prefixed with '+' or '-'
878 can be written to enable or disable controllers. A controller
954 Controllers chapter
960 The "cpu" controllers regulates distribution of CPU cycles. This
1829 This takes a similar format as the other controllers.
1859 controllers cannot prevent, thus warranting its own controller. For
2345 controllers are not covered.
2394 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2405 hierarchy could host any number of controllers. While this seemed to
2409 type controllers such as freezer which can be useful in all
2411 the fact that controllers couldn't be moved to another hierarchy once
2412 hierarchies were populated. Another issue was that all controllers
2417 In practice, these issues heavily limited which controllers could be
2420 as the cpu and cpuacct controllers, made sense to be put on the same
2428 used in general and what controllers was able to do.
2434 addition of controllers which existed only to identify membership,
2439 topologies of hierarchies other controllers might be on, each
2440 controller had to assume that all other controllers were attached to
2442 least very cumbersome, for controllers to cooperate with each other.
2444 In most use cases, putting controllers on hierarchies which are
2449 controllers. For example, a given configuration might not care about
2458 This didn't make sense for some controllers and those controllers
2484 cgroup controllers implemented a number of knobs which would never be
2505 settle it. Different controllers did different things.
2530 Multiple controllers struggled with internal tasks and came up with
2551 controllers completely ignoring hierarchical organization and treating
2553 cgroup. Some controllers exposed a large amount of inconsistent
2556 There also was no consistency across controllers. When a new cgroup
2557 was created, some controllers defaulted to not imposing extra
2565 controllers so that they expose minimal and consistent interfaces.
2641 that cgroup controllers should account and limit specific physical