Lines Matching refs:and
6 This document describes the changes made by unified hierarchy and
33 cgroup allows an arbitrary number of hierarchies and each hierarchy
46 on the same hierarchy and most configurations resort to putting each
48 the cpu and cpuacct controllers, make sense to put on the same
56 restricts how cgroup is used in general and what controllers can do.
60 The key may contain any varying number of entries and is unlimited in
61 length, which makes it highly awkward to handle and leads to addition
83 general and controller-specific interface issues are also addressed in
92 command. Note that this is still under development and scheduled to
97 All controllers which support the unified hierarchy and are not bound
98 to other hierarchies are automatically bound to unified hierarchy and
112 controller states are destroyed asynchronously and controllers may
116 moved out of the unified hierarchy and it may take some time for the
121 While useful for development and manual configurations, dynamically
122 moving controllers between the unified and other hierarchies is
124 the hierarchies and controller associations before starting using the
138 enabled on A. A's on B. B's on C and D. This coincides with the
150 the quotes). Controllers prefixed with '+' are enabled and '-'
163 other hierarchies and the content changes as controllers are bound to
164 and unbound from other hierarchies.
179 controller enabled and a controller can't be disabled if one or more
186 tasks belonging to the parent cgroup and its children cgroups. This
187 is inherently nasty as two different types of entities compete and
191 The cpu controller considers tasks and cgroups as equivalents and maps
194 and the number of internal tasks fluctuates - the ratios constantly
197 universal, and there are various other knobs which simply aren't
205 messy and significantly complicates the implementation.
208 happens between internal tasks and child cgroups and the behavior is
210 and knobs to tailor the behavior to specific workloads. Continuing
214 Multiple controllers struggle with internal tasks and came up with
216 use now are severely flawed and, furthermore, the widely different
221 worry about it and cgroup as a whole shows a consistent and logical
235 the restriction. Root contains tasks and anonymous resource
236 consumption which can't be associated with any other cgroup and
244 cgroup must create children and transfer all its tasks to the children
257 - It delivers events by forking and execing a userland binary
259 notification delivery. It's extremely heavy, slow and cumbersome to
272 unnecessarily complicated and probably done this way because event
278 and its descendants; otherwise, 1. poll and [id]notify events are
281 This is significantly lighter and simpler and trivially allows
284 in the subhierarchy and monitor events that it's interested in from
288 supported and the interface files "release_agent" and
318 - Tasks are kept in empty cpusets after hotplug and take on the masks
321 - A task can be moved into an empty cpuset, and again it takes on the
327 - use_hierarchy is on by default and the cgroup file for the flag is
337 global rbtree and treated like equal peers, regardless where they
345 reserve. A cgroup enjoys reclaim protection when it and all its
348 default and in the common case most cgroups are eligible for the
351 reclaim code, without the need for out-of-band data structures and
361 during runtime, and that requires users to overcommit. But doing
364 Since working set size estimation is hard and error prone, and
366 side of a looser limit and end up wasting precious resources.
374 and make corrections until the minimal memory footprint that still
377 In extreme cases, with many concurrent allocations and a complete
382 to limit this type of spillover and ultimately contain buggy or even
385 - The original control file names are unwieldy and inconsistent in
388 be manually counted by listening to memory.oom_control events, and
390 setting a threshold for that value and then counting those events.
391 Also, usage and limit files encode their units in the filename.
401 Very High Number, and a configured limit can be unset by echoing -1
402 into those files. But that very high number is implementation and
403 architecture dependent and not very descriptive. And while -1 can
407 memory.low, memory.high, and memory.max will use the string "max" to
408 indicate and set the highest possible value.
416 organization operations - creation of sub-cgroups and migration of
418 ownership and/or permissions on the cgroup directory and
438 internal details and userland-visible interface. Of course, this
445 Also, due to the specific nature, cgroup and its controllers don't
448 interfaces, unnecessary commitments to and exposing of internal
449 details, broken and dangerous implementations of various features.
452 its role and imperative given its nature. Some of the cgroup features
454 must be further abstracted and implemented as a different interface,
455 be it a system call or process-private filesystem, and survive through