Lines Matching refs:cgroups
103 multiple individual control groups, the plural form "cgroups" is used.
120 cgroups form a tree structure and every process in the system belongs
130 processes which belong to the cgroups consisting the inclusive
198 propagation into leaf cgroups. This allows protecting entire
217 A given cgroup may have multiple child cgroups forming a tree
283 different cgroups and are not subject to the no internal process
284 constraint - threaded controllers can be enabled on non-leaf cgroups
290 can't have populated child cgroups which aren't threaded. Because the
292 serve both as a threaded domain and a parent to domain cgroups.
356 between threads in a non-leaf cgroup and its child cgroups. Each
380 both cgroups.
420 files in the child cgroups. In the above example, enabling "cpu" on B
443 Non-root cgroups can distribute domain resources to their children
445 only domain cgroups which don't contain any processes can have domain
450 the leaves. This rules out situations where child cgroups compete
455 with any other cgroups and requires special treatment from most
499 cgroups in or nesting depth of a delegated sub-hierarchy; however,
517 common ancestor of the source and destination cgroups.
523 For an example, let's assume cgroups C0 and C1 have been delegated to
540 that both the source and destination cgroups are reachable from the
551 Migrating a process across cgroups is a relatively expensive operation
557 As such, migrating processes across cgroups frequently as a means to
568 Interface files for a cgroup and its children cgroups occupy the same
569 directory and it is possible to create children cgroups which collide
793 cgroups.
815 all cgroups.
830 common ancestor of the source and destination cgroups.
841 all cgroups.
859 common ancestor of the source and destination cgroups.
866 cgroups.
873 cgroups. Starts out empty.
887 A read-only flat-keyed file which exists on non-root cgroups.
901 Maximum allowed number of descent cgroups.
916 Total number of visible descendant cgroups.
919 Total number of dying descendant cgroups. A cgroup becomes
931 A read-write single value file which exists on non-root cgroups.
935 descendant cgroups. This means that all belonging processes will
943 of any ancestor cgroups. If any of ancestor cgroups is frozen, the
954 create new sub-cgroups.
957 A write-only single value file which exists in non-root cgroups.
960 Writing "1" to the file causes the cgroup and all descendant cgroups to
968 killing cgroups is a process directed operation, i.e. it affects
994 have placed RT processes into nonroot cgroups during the system boot
1024 cgroups. The default is "100".
1030 cgroups. The default is "0".
1041 A read-write two value file which exists on non-root cgroups.
1054 cgroups. The default is "0".
1065 A read-write single value file which exists on non-root cgroups.
1080 A read-write single value file which exists on non-root cgroups.
1124 cgroups.
1131 cgroups. The default is "0".
1143 all ancestor cgroups. If there is memory.min overcommitment
1144 (child cgroup or cgroups are requiring more protected memory
1157 cgroups. The default is "0".
1162 memory available in unprotected cgroups.
1169 all ancestor cgroups. If there is memory.low overcommitment
1170 (child cgroup or cgroups are requiring more protected memory
1180 cgroups. The default is "max".
1192 cgroups. The default is "max".
1213 cgroups. The default value is "0".
1227 memory.oom.group values of ancestor cgroups.
1230 A read-only flat-keyed file which exists on non-root cgroups.
1277 A read-only flat-keyed file which exists on non-root cgroups.
1429 A read-only nested-keyed file which exists on non-root cgroups.
1455 cgroups.
1462 cgroups. The default is "max".
1478 cgroups. The default is "max".
1484 A read-only flat-keyed file which exists on non-root cgroups.
1547 A memory area may be used by processes belonging to different cgroups.
1553 to be accessed repeatedly by other cgroups, it may make sense to use
1689 A read-write flat-keyed file which exists on non-root cgroups.
1710 cgroups.
1783 which are associated with different cgroups than the one the inode is
1791 changes over time, use cases where multiple cgroups write to a single
1796 strictly follows page ownership, multiple cgroups dirtying overlapping
1968 cgroups. The default is "max".
1973 A read-only single value file which exists on all cgroups.
2007 cpuset-enabled cgroups.
2029 cpuset-enabled cgroups.
2046 cpuset-enabled cgroups.
2080 cpuset-enabled cgroups.
2096 cpuset-enabled cgroups. This flag is owned by the parent cgroup
2121 4) There is no child cgroups with cpuset enabled. This is for
2128 cgroups with cpuset enabled.
2182 them to cgroups with BPF_CGROUP_DEVICE flag. On an attempt to access a
2206 A readwrite nested-keyed file that exists for all the cgroups
2253 A read-only flat-keyed file which exists on non-root cgroups.
2295 A read-only flat-keyed file shown in the non-root cgroups. It shows
2303 A read-write flat-keyed file shown in the non root cgroups. Allowed
2322 A read-only flat-keyed file which exists on non-root cgroups. The
2396 a set of cgroups and namespaces are intended to isolate processes the
2427 namespace is destroyed. The cgroupns root and the actual cgroups
2485 namespace root if they have proper access to external cgroups. For
2581 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2644 cgroup v1 allowed threads of a process to belong to different cgroups.
2656 in combination with thread granularity. cgroups were delegated to
2688 cgroup v1 allowed threads to be in any cgroups which created an
2690 children cgroups competed for resources. This was nasty as two
2694 The cpu controller considered threads and cgroups as equivalents and
2712 between internal tasks and child cgroups and the behavior was not
2739 all cgroups as if they were all located directly under the root
2762 that is per default unset. As a result, the set of cgroups that