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
206 propagation into leaf cgroups. This allows protecting entire
225 A given cgroup may have multiple child cgroups forming a tree
291 different cgroups and are not subject to the no internal process
292 constraint - threaded controllers can be enabled on non-leaf cgroups
298 can't have populated child cgroups which aren't threaded. Because the
300 serve both as a threaded domain and a parent to domain cgroups.
364 between threads in a non-leaf cgroup and its child cgroups. Each
388 both cgroups.
428 files in the child cgroups. In the above example, enabling "cpu" on B
451 Non-root cgroups can distribute domain resources to their children
453 only domain cgroups which don't contain any processes can have domain
458 the leaves. This rules out situations where child cgroups compete
463 with any other cgroups and requires special treatment from most
507 cgroups in or nesting depth of a delegated sub-hierarchy; however,
525 common ancestor of the source and destination cgroups.
531 For an example, let's assume cgroups C0 and C1 have been delegated to
548 that both the source and destination cgroups are reachable from the
559 Migrating a process across cgroups is a relatively expensive operation
565 As such, migrating processes across cgroups frequently as a means to
576 Interface files for a cgroup and its children cgroups occupy the same
577 directory and it is possible to create children cgroups which collide
801 cgroups.
823 all cgroups.
838 common ancestor of the source and destination cgroups.
849 all cgroups.
867 common ancestor of the source and destination cgroups.
874 cgroups.
881 cgroups. Starts out empty.
895 A read-only flat-keyed file which exists on non-root cgroups.
909 Maximum allowed number of descent cgroups.
924 Total number of visible descendant cgroups.
927 Total number of dying descendant cgroups. A cgroup becomes
939 A read-write single value file which exists on non-root cgroups.
943 descendant cgroups. This means that all belonging processes will
951 of any ancestor cgroups. If any of ancestor cgroups is frozen, the
962 create new sub-cgroups.
965 A write-only single value file which exists in non-root cgroups.
968 Writing "1" to the file causes the cgroup and all descendant cgroups to
976 killing cgroups is a process directed operation, i.e. it affects
994 be used to disable PSI accounting in the non-leaf cgroups.
1025 have placed RT processes into nonroot cgroups during the system boot
1055 cgroups. The default is "100".
1061 cgroups. The default is "0".
1072 A read-write two value file which exists on non-root cgroups.
1085 cgroups. The default is "0".
1096 A read-write single value file which exists on non-root cgroups.
1111 A read-write single value file which exists on non-root cgroups.
1155 cgroups.
1162 cgroups. The default is "0".
1174 all ancestor cgroups. If there is memory.min overcommitment
1175 (child cgroup or cgroups are requiring more protected memory
1188 cgroups. The default is "0".
1193 memory available in unprotected cgroups.
1200 all ancestor cgroups. If there is memory.low overcommitment
1201 (child cgroup or cgroups are requiring more protected memory
1211 cgroups. The default is "max".
1223 cgroups. The default is "max".
1243 A write-only nested-keyed file which exists for all cgroups.
1272 cgroups.
1279 cgroups. The default value is "0".
1293 memory.oom.group values of ancestor cgroups.
1296 A read-only flat-keyed file which exists on non-root cgroups.
1346 A read-only flat-keyed file which exists on non-root cgroups.
1529 A read-only nested-keyed file which exists on non-root cgroups.
1555 cgroups.
1562 cgroups. The default is "max".
1578 cgroups. The default is "max".
1584 A read-only flat-keyed file which exists on non-root cgroups.
1610 cgroups.
1617 cgroups. The default is "max".
1662 A memory area may be used by processes belonging to different cgroups.
1668 to be accessed repeatedly by other cgroups, it may make sense to use
1804 A read-write flat-keyed file which exists on non-root cgroups.
1825 cgroups.
1898 which are associated with different cgroups than the one the inode is
1906 changes over time, use cases where multiple cgroups write to a single
1911 strictly follows page ownership, multiple cgroups dirtying overlapping
2083 cgroups. The default is "max".
2088 A read-only single value file which exists on all cgroups.
2122 cpuset-enabled cgroups.
2144 cpuset-enabled cgroups.
2161 cpuset-enabled cgroups.
2195 cpuset-enabled cgroups.
2211 cpuset-enabled cgroups. This flag is owned by the parent cgroup
2223 cannot be changed. All other non-root cgroups start out as
2315 them to cgroups with BPF_CGROUP_DEVICE flag. On an attempt to access a
2339 A readwrite nested-keyed file that exists for all the cgroups
2386 A read-only flat-keyed file which exists on non-root cgroups.
2433 A read-only flat-keyed file shown in the non-root cgroups. It shows
2441 A read-write flat-keyed file shown in the non root cgroups. Allowed
2460 A read-only flat-keyed file which exists on non-root cgroups. The
2534 a set of cgroups and namespaces are intended to isolate processes the
2565 namespace is destroyed. The cgroupns root and the actual cgroups
2623 namespace root if they have proper access to external cgroups. For
2719 - /proc/cgroups is meaningless for v2. Use "cgroup.controllers" file
2782 cgroup v1 allowed threads of a process to belong to different cgroups.
2794 in combination with thread granularity. cgroups were delegated to
2826 cgroup v1 allowed threads to be in any cgroups which created an
2828 children cgroups competed for resources. This was nasty as two
2832 The cpu controller considered threads and cgroups as equivalents and
2850 between internal tasks and child cgroups and the behavior was not
2877 all cgroups as if they were all located directly under the root
2900 that is per default unset. As a result, the set of cgroups that