Lines Matching refs:cgroups
93 multiple individual control groups, the plural form "cgroups" is used.
110 cgroups form a tree structure and every process in the system belongs
120 processes which belong to the cgroups consisting the inclusive
190 A given cgroup may have multiple child cgroups forming a tree
256 different cgroups and are not subject to the no internal process
257 constraint - threaded controllers can be enabled on non-leaf cgroups
263 can't have populated child cgroups which aren't threaded. Because the
265 serve both as a threaded domain and a parent to domain cgroups.
329 between threads in a non-leaf cgroup and its child cgroups. Each
353 both cgroups.
393 files in the child cgroups. In the above example, enabling "cpu" on B
416 Non-root cgroups can distribute domain resources to their children
418 only domain cgroups which don't contain any processes can have domain
423 the leaves. This rules out situations where child cgroups compete
428 with any other cgroups and requires special treatment from most
472 cgroups in or nesting depth of a delegated sub-hierarchy; however,
490 common ancestor of the source and destination cgroups.
496 For an example, let's assume cgroups C0 and C1 have been delegated to
513 that both the source and destination cgroups are reachable from the
524 Migrating a process across cgroups is a relatively expensive operation
530 As such, migrating processes across cgroups frequently as a means to
541 Interface files for a cgroup and its children cgroups occupy the same
542 directory and it is possible to create children cgroups which collide
763 cgroups.
785 all cgroups.
800 common ancestor of the source and destination cgroups.
811 all cgroups.
829 common ancestor of the source and destination cgroups.
836 cgroups.
843 cgroups. Starts out empty.
857 A read-only flat-keyed file which exists on non-root cgroups.
869 Maximum allowed number of descent cgroups.
884 Total number of visible descendant cgroups.
887 Total number of dying descendant cgroups. A cgroup becomes
913 have placed RT processes into nonroot cgroups during the system boot
924 A read-only flat-keyed file which exists on non-root cgroups.
941 cgroups. The default is "100".
947 cgroups. The default is "0".
958 A read-write two value file which exists on non-root cgroups.
1002 cgroups.
1009 cgroups. The default is "0".
1018 all ancestor cgroups. If there is memory.min overcommitment
1019 (child cgroup or cgroups are requiring more protected memory
1032 cgroups. The default is "0".
1037 from unprotected cgroups.
1040 all ancestor cgroups. If there is memory.low overcommitment
1041 (child cgroup or cgroups are requiring more protected memory
1051 cgroups. The default is "max".
1063 cgroups. The default is "max".
1077 cgroups. The default value is "0".
1091 memory.oom.group values of ancestor cgroups.
1094 A read-only flat-keyed file which exists on non-root cgroups.
1135 A read-only flat-keyed file which exists on non-root cgroups.
1241 cgroups.
1248 cgroups. The default is "max".
1254 A read-only flat-keyed file which exists on non-root cgroups.
1307 A memory area may be used by processes belonging to different cgroups.
1313 to be accessed repeatedly by other cgroups, it may make sense to use
1333 cgroups.
1353 A read-write flat-keyed file which exists on non-root cgroups.
1374 cgroups.
1441 which are associated with different cgroups than the one the inode is
1449 changes over time, use cases where multiple cgroups write to a single
1454 strictly follows page ownership, multiple cgroups dirtying overlapping
1572 cgroups. The default is "max".
1577 A read-only single value file which exists on all cgroups.
1601 to cgroups. On an attempt to access a device file, corresponding
1625 A readwrite nested-keyed file that exists for all the cgroups
1712 a set of cgroups and namespaces are intended to isolate processes the
1743 namespace is destroyed. The cgroupns root and the actual cgroups
1801 namespace root if they have proper access to external cgroups. For
1895 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
1958 cgroup v1 allowed threads of a process to belong to different cgroups.
1970 in combination with thread granularity. cgroups were delegated to
2002 cgroup v1 allowed threads to be in any cgroups which created an
2004 children cgroups competed for resources. This was nasty as two
2008 The cpu controller considered threads and cgroups as equivalents and
2026 between internal tasks and child cgroups and the behavior was not
2053 all cgroups as if they were all located directly under the root
2076 that is per default unset. As a result, the set of cgroups that