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
301 cgroup v2 supports thread granularity for a subset of controllers to
309 Controllers which support thread mode are called threaded controllers.
310 The ones which don't are called domain controllers.
321 constraint - threaded controllers can be enabled on non-leaf cgroups
349 controllers enabled or populated domain children. The root is
364 cgroup becomes threaded or threaded controllers are enabled in the
385 Only threaded controllers can be enabled in a threaded subtree. When
396 Currently, the following controllers are threaded and can be enabled
427 Controlling Controllers
433 Each cgroup has a "cgroup.controllers" file which lists all
434 controllers available for the cgroup to enable::
436 # cat cgroup.controllers
439 No controller is enabled by default. Controllers can be enabled and
444 Only controllers which are listed in "cgroup.controllers" can be
451 Consider the following sub-hierarchy. The enabled controllers are
478 can only contain controllers which are enabled in the parent's
490 controllers enabled in their "cgroup.subtree_control" files.
500 controllers. How resource consumption in the root cgroup is governed
502 refer to the Non-normative information section in the Controllers
510 children before enabling controllers in its "cgroup.subtree_control"
538 of all resource controllers are hierarchical and regardless of what
631 cgroup controllers implement several resource distribution schemes
753 reading; however, controllers may allow omitting later fields or
851 It can't be populated or have controllers enabled. It may
911 cgroup.controllers
915 It shows space separated list of all controllers available to
916 the cgroup. The controllers are not ordered.
922 When read, it shows space separated list of the controllers
926 Space separated list of controllers prefixed with '+' or '-'
927 can be written to enable or disable controllers. A controller
1041 Controllers chapter
1049 The "cpu" controllers regulates distribution of CPU cycles. This
2074 This takes a similar format as the other controllers.
2166 controllers cannot prevent, thus warranting its own controller. For
2832 controllers are not covered.
2881 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2892 hierarchy could host any number of controllers. While this seemed to
2896 type controllers such as freezer which can be useful in all
2898 the fact that controllers couldn't be moved to another hierarchy once
2899 hierarchies were populated. Another issue was that all controllers
2904 In practice, these issues heavily limited which controllers could be
2907 as the cpu and cpuacct controllers, made sense to be put on the same
2915 used in general and what controllers was able to do.
2921 addition of controllers which existed only to identify membership,
2926 topologies of hierarchies other controllers might be on, each
2927 controller had to assume that all other controllers were attached to
2929 least very cumbersome, for controllers to cooperate with each other.
2931 In most use cases, putting controllers on hierarchies which are
2936 controllers. For example, a given configuration might not care about
2945 This didn't make sense for some controllers and those controllers
2971 cgroup controllers implemented a number of knobs which would never be
2992 settle it. Different controllers did different things.
3017 Multiple controllers struggled with internal tasks and came up with
3038 controllers completely ignoring hierarchical organization and treating
3040 cgroup. Some controllers exposed a large amount of inconsistent
3043 There also was no consistency across controllers. When a new cgroup
3044 was created, some controllers defaulted to not imposing extra
3052 controllers so that they expose minimal and consistent interfaces.
3128 that cgroup controllers should account and limit specific physical