Lines Matching full:controllers
27 2-4. Controlling Controllers
46 5. Controllers
102 qualifier as in "cgroup controllers". When explicitly referring to
113 cgroup is largely composed of two parts - the core and controllers.
117 although there are utility controllers which serve purposes other than
127 Following certain structural constraints, controllers may be enabled or
149 controllers which support v2 and are not bound to a v1 hierarchy are
151 Controllers which are not in active use in the v2 hierarchy can be
157 controller states are destroyed asynchronously and controllers may
163 to inter-controller dependencies, other controllers may need to be
167 controllers dynamically between the v2 and other hierarchies is
170 controllers after system boot.
173 automount the v1 cgroup filesystem and so hijack all controllers
176 disabling controllers in v1 and make them always available in v2.
192 controllers, and then seeding it with CLONE_INTO_CGROUP is
272 cgroup v2 supports thread granularity for a subset of controllers to
280 Controllers which support thread mode are called threaded controllers.
281 The ones which don't are called domain controllers.
292 constraint - threaded controllers can be enabled on non-leaf cgroups
320 controllers enabled or populated domain children. The root is
335 cgroup becomes threaded or threaded controllers are enabled in the
356 Only threaded controllers can be enabled in a threaded subtree. When
391 Controlling Controllers
397 Each cgroup has a "cgroup.controllers" file which lists all
398 controllers available for the cgroup to enable::
400 # cat cgroup.controllers
403 No controller is enabled by default. Controllers can be enabled and
408 Only controllers which are listed in "cgroup.controllers" can be
415 Consider the following sub-hierarchy. The enabled controllers are
442 can only contain controllers which are enabled in the parent's
454 controllers enabled in their "cgroup.subtree_control" files.
464 controllers. How resource consumption in the root cgroup is governed
466 refer to the Non-normative information section in the Controllers
474 children before enabling controllers in its "cgroup.subtree_control"
502 of all resource controllers are hierarchical and regardless of what
595 cgroup controllers implement several resource distribution schemes
717 reading; however, controllers may allow omitting later fields or
815 It can't be populated or have controllers enabled. It may
875 cgroup.controllers
879 It shows space separated list of all controllers available to
880 the cgroup. The controllers are not ordered.
886 When read, it shows space separated list of the controllers
890 Space separated list of controllers prefixed with '+' or '-'
891 can be written to enable or disable controllers. A controller
1005 Controllers chapter
1013 The "cpu" controllers regulates distribution of CPU cycles. This
2000 This takes a similar format as the other controllers.
2090 controllers cannot prevent, thus warranting its own controller. For
2690 controllers are not covered.
2739 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2750 hierarchy could host any number of controllers. While this seemed to
2754 type controllers such as freezer which can be useful in all
2756 the fact that controllers couldn't be moved to another hierarchy once
2757 hierarchies were populated. Another issue was that all controllers
2762 In practice, these issues heavily limited which controllers could be
2765 as the cpu and cpuacct controllers, made sense to be put on the same
2773 used in general and what controllers was able to do.
2779 addition of controllers which existed only to identify membership,
2784 topologies of hierarchies other controllers might be on, each
2785 controller had to assume that all other controllers were attached to
2787 least very cumbersome, for controllers to cooperate with each other.
2789 In most use cases, putting controllers on hierarchies which are
2794 controllers. For example, a given configuration might not care about
2803 This didn't make sense for some controllers and those controllers
2829 cgroup controllers implemented a number of knobs which would never be
2850 settle it. Different controllers did different things.
2875 Multiple controllers struggled with internal tasks and came up with
2896 controllers completely ignoring hierarchical organization and treating
2898 cgroup. Some controllers exposed a large amount of inconsistent
2901 There also was no consistency across controllers. When a new cgroup
2902 was created, some controllers defaulted to not imposing extra
2910 controllers so that they expose minimal and consistent interfaces.
2986 that cgroup controllers should account and limit specific physical