Lines Matching refs:cgroups
97 multiple individual control groups, the plural form "cgroups" is used.
114 cgroups form a tree structure and every process in the system belongs
124 processes which belong to the cgroups consisting the inclusive
195 propagation into leaf cgroups. This allows protecting entire
214 A given cgroup may have multiple child cgroups forming a tree
280 different cgroups and are not subject to the no internal process
281 constraint - threaded controllers can be enabled on non-leaf cgroups
287 can't have populated child cgroups which aren't threaded. Because the
289 serve both as a threaded domain and a parent to domain cgroups.
353 between threads in a non-leaf cgroup and its child cgroups. Each
377 both cgroups.
417 files in the child cgroups. In the above example, enabling "cpu" on B
440 Non-root cgroups can distribute domain resources to their children
442 only domain cgroups which don't contain any processes can have domain
447 the leaves. This rules out situations where child cgroups compete
452 with any other cgroups and requires special treatment from most
496 cgroups in or nesting depth of a delegated sub-hierarchy; however,
514 common ancestor of the source and destination cgroups.
520 For an example, let's assume cgroups C0 and C1 have been delegated to
537 that both the source and destination cgroups are reachable from the
548 Migrating a process across cgroups is a relatively expensive operation
554 As such, migrating processes across cgroups frequently as a means to
565 Interface files for a cgroup and its children cgroups occupy the same
566 directory and it is possible to create children cgroups which collide
791 cgroups.
813 all cgroups.
828 common ancestor of the source and destination cgroups.
839 all cgroups.
857 common ancestor of the source and destination cgroups.
864 cgroups.
871 cgroups. Starts out empty.
885 A read-only flat-keyed file which exists on non-root cgroups.
899 Maximum allowed number of descent cgroups.
914 Total number of visible descendant cgroups.
917 Total number of dying descendant cgroups. A cgroup becomes
929 A read-write single value file which exists on non-root cgroups.
933 descendant cgroups. This means that all belonging processes will
941 of any ancestor cgroups. If any of ancestor cgroups is frozen, the
952 create new sub-cgroups.
975 have placed RT processes into nonroot cgroups during the system boot
1003 cgroups. The default is "100".
1009 cgroups. The default is "0".
1020 A read-write two value file which exists on non-root cgroups.
1032 A read-only nested-key file which exists on non-root cgroups.
1038 A read-write single value file which exists on non-root cgroups.
1053 A read-write single value file which exists on non-root cgroups.
1097 cgroups.
1104 cgroups. The default is "0".
1116 all ancestor cgroups. If there is memory.min overcommitment
1117 (child cgroup or cgroups are requiring more protected memory
1130 cgroups. The default is "0".
1135 memory available in unprotected cgroups.
1142 all ancestor cgroups. If there is memory.low overcommitment
1143 (child cgroup or cgroups are requiring more protected memory
1153 cgroups. The default is "max".
1165 cgroups. The default is "max".
1186 cgroups. The default value is "0".
1200 memory.oom.group values of ancestor cgroups.
1203 A read-only flat-keyed file which exists on non-root cgroups.
1250 A read-only flat-keyed file which exists on non-root cgroups.
1387 A read-only nested-keyed file which exists on non-root cgroups.
1413 cgroups.
1420 cgroups. The default is "max".
1436 cgroups. The default is "max".
1442 A read-only flat-keyed file which exists on non-root cgroups.
1467 A read-only nested-key file which exists on non-root cgroups.
1505 A memory area may be used by processes belonging to different cgroups.
1511 to be accessed repeatedly by other cgroups, it may make sense to use
1647 A read-write flat-keyed file which exists on non-root cgroups.
1668 cgroups.
1706 A read-only nested-key file which exists on non-root cgroups.
1741 which are associated with different cgroups than the one the inode is
1749 changes over time, use cases where multiple cgroups write to a single
1754 strictly follows page ownership, multiple cgroups dirtying overlapping
1872 cgroups. The default is "max".
1877 A read-only single value file which exists on all cgroups.
1911 cpuset-enabled cgroups.
1933 cpuset-enabled cgroups.
1950 cpuset-enabled cgroups.
1973 cpuset-enabled cgroups.
1989 cpuset-enabled cgroups. This flag is owned by the parent cgroup
2012 4) There is no child cgroups with cpuset enabled. This is for
2019 cgroups with cpuset enabled.
2071 to cgroups. On an attempt to access a device file, corresponding
2095 A readwrite nested-keyed file that exists for all the cgroups
2142 A read-only flat-keyed file which exists on non-root cgroups.
2209 a set of cgroups and namespaces are intended to isolate processes the
2240 namespace is destroyed. The cgroupns root and the actual cgroups
2298 namespace root if they have proper access to external cgroups. For
2394 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2457 cgroup v1 allowed threads of a process to belong to different cgroups.
2469 in combination with thread granularity. cgroups were delegated to
2501 cgroup v1 allowed threads to be in any cgroups which created an
2503 children cgroups competed for resources. This was nasty as two
2507 The cpu controller considered threads and cgroups as equivalents and
2525 between internal tasks and child cgroups and the behavior was not
2552 all cgroups as if they were all located directly under the root
2575 that is per default unset. As a result, the set of cgroups that