Lines Matching refs:cgroups
98 multiple individual control groups, the plural form "cgroups" is used.
115 cgroups form a tree structure and every process in the system belongs
125 processes which belong to the cgroups consisting the inclusive
196 propagation into leaf cgroups. This allows protecting entire
215 A given cgroup may have multiple child cgroups forming a tree
281 different cgroups and are not subject to the no internal process
282 constraint - threaded controllers can be enabled on non-leaf cgroups
288 can't have populated child cgroups which aren't threaded. Because the
290 serve both as a threaded domain and a parent to domain cgroups.
354 between threads in a non-leaf cgroup and its child cgroups. Each
378 both cgroups.
418 files in the child cgroups. In the above example, enabling "cpu" on B
441 Non-root cgroups can distribute domain resources to their children
443 only domain cgroups which don't contain any processes can have domain
448 the leaves. This rules out situations where child cgroups compete
453 with any other cgroups and requires special treatment from most
497 cgroups in or nesting depth of a delegated sub-hierarchy; however,
515 common ancestor of the source and destination cgroups.
521 For an example, let's assume cgroups C0 and C1 have been delegated to
538 that both the source and destination cgroups are reachable from the
549 Migrating a process across cgroups is a relatively expensive operation
555 As such, migrating processes across cgroups frequently as a means to
566 Interface files for a cgroup and its children cgroups occupy the same
567 directory and it is possible to create children cgroups which collide
792 cgroups.
814 all cgroups.
829 common ancestor of the source and destination cgroups.
840 all cgroups.
858 common ancestor of the source and destination cgroups.
865 cgroups.
872 cgroups. Starts out empty.
886 A read-only flat-keyed file which exists on non-root cgroups.
900 Maximum allowed number of descent cgroups.
915 Total number of visible descendant cgroups.
918 Total number of dying descendant cgroups. A cgroup becomes
930 A read-write single value file which exists on non-root cgroups.
934 descendant cgroups. This means that all belonging processes will
942 of any ancestor cgroups. If any of ancestor cgroups is frozen, the
953 create new sub-cgroups.
976 have placed RT processes into nonroot cgroups during the system boot
1004 cgroups. The default is "100".
1010 cgroups. The default is "0".
1021 A read-write two value file which exists on non-root cgroups.
1033 A read-only nested-key file which exists on non-root cgroups.
1039 A read-write single value file which exists on non-root cgroups.
1054 A read-write single value file which exists on non-root cgroups.
1098 cgroups.
1105 cgroups. The default is "0".
1117 all ancestor cgroups. If there is memory.min overcommitment
1118 (child cgroup or cgroups are requiring more protected memory
1131 cgroups. The default is "0".
1136 memory available in unprotected cgroups.
1143 all ancestor cgroups. If there is memory.low overcommitment
1144 (child cgroup or cgroups are requiring more protected memory
1154 cgroups. The default is "max".
1166 cgroups. The default is "max".
1187 cgroups. The default value is "0".
1201 memory.oom.group values of ancestor cgroups.
1204 A read-only flat-keyed file which exists on non-root cgroups.
1251 A read-only flat-keyed file which exists on non-root cgroups.
1388 A read-only nested-keyed file which exists on non-root cgroups.
1414 cgroups.
1421 cgroups. The default is "max".
1437 cgroups. The default is "max".
1443 A read-only flat-keyed file which exists on non-root cgroups.
1468 A read-only nested-key file which exists on non-root cgroups.
1506 A memory area may be used by processes belonging to different cgroups.
1512 to be accessed repeatedly by other cgroups, it may make sense to use
1648 A read-write flat-keyed file which exists on non-root cgroups.
1669 cgroups.
1707 A read-only nested-key file which exists on non-root cgroups.
1742 which are associated with different cgroups than the one the inode is
1750 changes over time, use cases where multiple cgroups write to a single
1755 strictly follows page ownership, multiple cgroups dirtying overlapping
1927 cgroups. The default is "max".
1932 A read-only single value file which exists on all cgroups.
1966 cpuset-enabled cgroups.
1988 cpuset-enabled cgroups.
2005 cpuset-enabled cgroups.
2028 cpuset-enabled cgroups.
2044 cpuset-enabled cgroups. This flag is owned by the parent cgroup
2067 4) There is no child cgroups with cpuset enabled. This is for
2074 cgroups with cpuset enabled.
2126 to cgroups. On an attempt to access a device file, corresponding
2150 A readwrite nested-keyed file that exists for all the cgroups
2197 A read-only flat-keyed file which exists on non-root cgroups.
2264 a set of cgroups and namespaces are intended to isolate processes the
2295 namespace is destroyed. The cgroupns root and the actual cgroups
2353 namespace root if they have proper access to external cgroups. For
2449 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2512 cgroup v1 allowed threads of a process to belong to different cgroups.
2524 in combination with thread granularity. cgroups were delegated to
2556 cgroup v1 allowed threads to be in any cgroups which created an
2558 children cgroups competed for resources. This was nasty as two
2562 The cpu controller considered threads and cgroups as equivalents and
2580 between internal tasks and child cgroups and the behavior was not
2607 all cgroups as if they were all located directly under the root
2630 that is per default unset. As a result, the set of cgroups that