Lines Matching refs:cgroups
95 multiple individual control groups, the plural form "cgroups" is used.
112 cgroups form a tree structure and every process in the system belongs
122 processes which belong to the cgroups consisting the inclusive
201 A given cgroup may have multiple child cgroups forming a tree
267 different cgroups and are not subject to the no internal process
268 constraint - threaded controllers can be enabled on non-leaf cgroups
274 can't have populated child cgroups which aren't threaded. Because the
276 serve both as a threaded domain and a parent to domain cgroups.
340 between threads in a non-leaf cgroup and its child cgroups. Each
364 both cgroups.
404 files in the child cgroups. In the above example, enabling "cpu" on B
427 Non-root cgroups can distribute domain resources to their children
429 only domain cgroups which don't contain any processes can have domain
434 the leaves. This rules out situations where child cgroups compete
439 with any other cgroups and requires special treatment from most
483 cgroups in or nesting depth of a delegated sub-hierarchy; however,
501 common ancestor of the source and destination cgroups.
507 For an example, let's assume cgroups C0 and C1 have been delegated to
524 that both the source and destination cgroups are reachable from the
535 Migrating a process across cgroups is a relatively expensive operation
541 As such, migrating processes across cgroups frequently as a means to
552 Interface files for a cgroup and its children cgroups occupy the same
553 directory and it is possible to create children cgroups which collide
780 cgroups.
802 all cgroups.
817 common ancestor of the source and destination cgroups.
828 all cgroups.
846 common ancestor of the source and destination cgroups.
853 cgroups.
860 cgroups. Starts out empty.
874 A read-only flat-keyed file which exists on non-root cgroups.
888 Maximum allowed number of descent cgroups.
903 Total number of visible descendant cgroups.
906 Total number of dying descendant cgroups. A cgroup becomes
918 A read-write single value file which exists on non-root cgroups.
922 descendant cgroups. This means that all belonging processes will
930 of any ancestor cgroups. If any of ancestor cgroups is frozen, the
941 create new sub-cgroups.
964 have placed RT processes into nonroot cgroups during the system boot
975 A read-only flat-keyed file which exists on non-root cgroups.
992 cgroups. The default is "100".
998 cgroups. The default is "0".
1009 A read-write two value file which exists on non-root cgroups.
1021 A read-only nested-key file which exists on non-root cgroups.
1027 A read-write single value file which exists on non-root cgroups.
1042 A read-write single value file which exists on non-root cgroups.
1086 cgroups.
1093 cgroups. The default is "0".
1105 all ancestor cgroups. If there is memory.min overcommitment
1106 (child cgroup or cgroups are requiring more protected memory
1119 cgroups. The default is "0".
1124 from unprotected cgroups. Above the effective low boundary (or
1130 all ancestor cgroups. If there is memory.low overcommitment
1131 (child cgroup or cgroups are requiring more protected memory
1141 cgroups. The default is "max".
1153 cgroups. The default is "max".
1167 cgroups. The default value is "0".
1181 memory.oom.group values of ancestor cgroups.
1184 A read-only flat-keyed file which exists on non-root cgroups.
1239 A read-only flat-keyed file which exists on non-root cgroups.
1361 cgroups.
1368 cgroups. The default is "max".
1374 A read-only flat-keyed file which exists on non-root cgroups.
1395 A read-only nested-key file which exists on non-root cgroups.
1433 A memory area may be used by processes belonging to different cgroups.
1439 to be accessed repeatedly by other cgroups, it may make sense to use
1459 cgroups.
1576 A read-write flat-keyed file which exists on non-root cgroups.
1597 cgroups.
1635 A read-only nested-key file which exists on non-root cgroups.
1670 which are associated with different cgroups than the one the inode is
1678 changes over time, use cases where multiple cgroups write to a single
1683 strictly follows page ownership, multiple cgroups dirtying overlapping
1801 cgroups. The default is "max".
1806 A read-only single value file which exists on all cgroups.
1840 cpuset-enabled cgroups.
1862 cpuset-enabled cgroups.
1879 cpuset-enabled cgroups.
1902 cpuset-enabled cgroups.
1918 cpuset-enabled cgroups. This flag is owned by the parent cgroup
1941 4) There is no child cgroups with cpuset enabled. This is for
1948 cgroups with cpuset enabled.
2000 to cgroups. On an attempt to access a device file, corresponding
2024 A readwrite nested-keyed file that exists for all the cgroups
2111 a set of cgroups and namespaces are intended to isolate processes the
2142 namespace is destroyed. The cgroupns root and the actual cgroups
2200 namespace root if they have proper access to external cgroups. For
2296 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2359 cgroup v1 allowed threads of a process to belong to different cgroups.
2371 in combination with thread granularity. cgroups were delegated to
2403 cgroup v1 allowed threads to be in any cgroups which created an
2405 children cgroups competed for resources. This was nasty as two
2409 The cpu controller considered threads and cgroups as equivalents and
2427 between internal tasks and child cgroups and the behavior was not
2454 all cgroups as if they were all located directly under the root
2477 that is per default unset. As a result, the set of cgroups that