Lines Matching full:controllers
25 2-4. Controlling Controllers
44 5. Controllers
92 qualifier as in "cgroup controllers". When explicitly referring to
103 cgroup is largely composed of two parts - the core and controllers.
107 although there are utility controllers which serve purposes other than
117 Following certain structural constraints, controllers may be enabled or
139 controllers which support v2 and are not bound to a v1 hierarchy are
141 Controllers which are not in active use in the v2 hierarchy can be
147 controller states are destroyed asynchronously and controllers may
153 to inter-controller dependencies, other controllers may need to be
157 controllers dynamically between the v2 and other hierarchies is
160 controllers after system boot.
163 automount the v1 cgroup filesystem and so hijack all controllers
166 disabling controllers in v1 and make them always available in v2.
237 cgroup v2 supports thread granularity for a subset of controllers to
245 Controllers which support thread mode are called threaded controllers.
246 The ones which don't are called domain controllers.
257 constraint - threaded controllers can be enabled on non-leaf cgroups
285 controllers enabled or populated domain children. The root is
300 cgroup becomes threaded or threaded controllers are enabled in the
321 Only threaded controllers can be enabled in a threaded subtree. When
356 Controlling Controllers
362 Each cgroup has a "cgroup.controllers" file which lists all
363 controllers available for the cgroup to enable::
365 # cat cgroup.controllers
368 No controller is enabled by default. Controllers can be enabled and
373 Only controllers which are listed in "cgroup.controllers" can be
380 Consider the following sub-hierarchy. The enabled controllers are
407 can only contain controllers which are enabled in the parent's
419 controllers enabled in their "cgroup.subtree_control" files.
429 controllers. How resource consumption in the root cgroup is governed
431 refer to the Non-normative information section in the Controllers
439 children before enabling controllers in its "cgroup.subtree_control"
467 of all resource controllers are hierarchical and regardless of what
560 cgroup controllers implement several resource distribution schemes
679 reading; however, controllers may allow omitting later fields or
774 It can't be populated or have controllers enabled. It may
834 cgroup.controllers
838 It shows space separated list of all controllers available to
839 the cgroup. The controllers are not ordered.
845 When read, it shows space separated list of the controllers
849 Space separated list of controllers prefixed with '+' or '-'
850 can be written to enable or disable controllers. A controller
899 Controllers chapter
905 The "cpu" controllers regulates distribution of CPU cycles. This
1529 This takes a similar format as the other controllers.
1559 controllers cannot prevent, thus warranting its own controller. For
1848 controllers are not covered.
1895 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
1906 hierarchy could host any number of controllers. While this seemed to
1910 type controllers such as freezer which can be useful in all
1912 the fact that controllers couldn't be moved to another hierarchy once
1913 hierarchies were populated. Another issue was that all controllers
1918 In practice, these issues heavily limited which controllers could be
1921 as the cpu and cpuacct controllers, made sense to be put on the same
1929 used in general and what controllers was able to do.
1935 addition of controllers which existed only to identify membership,
1940 topologies of hierarchies other controllers might be on, each
1941 controller had to assume that all other controllers were attached to
1943 least very cumbersome, for controllers to cooperate with each other.
1945 In most use cases, putting controllers on hierarchies which are
1950 controllers. For example, a given configuration might not care about
1959 This didn't make sense for some controllers and those controllers
1985 cgroup controllers implemented a number of knobs which would never be
2006 settle it. Different controllers did different things.
2031 Multiple controllers struggled with internal tasks and came up with
2052 controllers completely ignoring hierarchical organization and treating
2054 cgroup. Some controllers exposed a large amount of inconsistent
2057 There also was no consistency across controllers. When a new cgroup
2058 was created, some controllers defaulted to not imposing extra
2066 controllers so that they expose minimal and consistent interfaces.
2140 that cgroup controllers should account and limit specific physical