Lines Matching full:which
123 although there are utility controllers which serve purposes other than
136 processes which belong to the cgroups consisting the inclusive
155 controllers which support v2 and are not bound to a v1 hierarchy are
157 Controllers which are not in active use in the v2 hierarchy can be
262 Initially, only the root cgroup exists to which all processes belong.
269 "cgroup.procs". When read, it lists the PIDs of all processes which
287 A cgroup which doesn't have any children or live processes can be
288 destroyed by removing the directory. Note that a cgroup which doesn't
317 process belong to the same cgroup, which also serves as the resource
318 domain to host resource consumptions which are not specific to a
322 Controllers which support thread mode are called threaded controllers.
323 The ones which don't are called domain controllers.
328 of a threaded subtree, that is, the nearest ancestor which is not
340 can't have populated child cgroups which aren't threaded. Because the
345 "cgroup.type" file which indicates whether the cgroup is a normal
346 domain, a domain which is serving as the domain of a threaded subtree,
370 C is created as a domain but isn't connected to a parent which can
373 these cases. Operations which fail due to invalid topology use
401 threads in the cgroup and its descendants. All consumptions which
420 Each non-root cgroup has a "cgroup.events" file which contains
455 Each cgroup has a "cgroup.controllers" file which lists all
466 Only controllers which are listed in "cgroup.controllers" can be
490 controller interface files - anything which doesn't start with
500 can only contain controllers which are enabled in the parent's
511 only domain cgroups which don't contain any processes can have domain
515 of the hierarchy which has it enabled, processes are always only on
520 processes and anonymous resource consumption which can't be associated
600 Let's also say U0 wants to write the PID of a process which is
609 namespace of the process which is attempting the migration. If either
637 directory and it is possible to create children cgroups which collide
645 start or end with terms which are often used in categorizing workloads
665 weight against the sum. As only children which can make use of the
691 Limits are in the range [0, max] and defaults to "max", which is noop.
708 soft boundaries. Protections can also be over-committed in which case
712 Protections are in the range [0, max] and defaults to 0, which is
731 Allocations are in the range [0, max] and defaults to 0, which is no
825 For example, a setting which is keyed by major:minor device numbers
851 - For events which are not very high frequency, an interface file
852 "events" should be created which lists event key value pairs.
863 A read-write single value file which exists on non-root
866 When read, it indicates the current type of the cgroup, which
871 - "domain threaded" : A threaded domain cgroup which is
874 - "domain invalid" : A cgroup which is in an invalid state.
878 - "threaded" : A threaded cgroup which is a member of a
885 A read-write new-line separated values file which exists on
888 When read, it lists the PIDs of all processes which belong to
911 A read-write new-line separated values file which exists on
914 When read, it lists the TIDs of all threads which belong to
936 A read-only space separated values file which exists on all
943 A read-write space separated values file which exists on all
947 which are enabled to control resource distribution from the
958 A read-only flat-keyed file which exists on non-root cgroups.
992 in dying state for some time undefined time (which can depend
999 limits, which were active at the moment of cgroup deletion.
1010 A read-only flat-keyed file which exists in non-root cgroups.
1028 A read-write single value file which exists on non-root cgroups.
1054 A write-only single value file which exists in non-root cgroups.
1082 deep level of the hierarchy, in which case this control attribute can
1105 base and it does not account for the frequency at which tasks are executed.
1107 cpufreq governor about the minimum desired frequency which should always be
1108 provided by a CPU, as well as the maximum desired frequency, which should not
1149 It always reports the following three stats, which account for all the
1156 and the following five when the controller is enabled, which account for
1166 A read-write single value file which exists on non-root
1180 A read-write single value file which exists on non-root
1196 A read-write two value file which exists on non-root cgroups.
1203 which indicates that the group may consume up to $MAX in each
1210 A read-write single value file which exists on non-root
1226 A read-write single value file which exists on non-root cgroups.
1244 A read-write single value file which exists on non-root cgroups.
1258 A read-write single value file which exists on non-root cgroups.
1295 All memory amounts are in bytes. If a value which is not aligned to
1300 A read-only single value file which exists on non-root
1307 A read-write single value file which exists on non-root
1333 A read-write single value file which exists on non-root
1356 A read-write single value file which exists on non-root
1382 A read-write single value file which exists on non-root
1411 A write-only nested-keyed file which exists for all cgroups.
1446 A read-write single value file which exists on non-root cgroups.
1456 A read-write single value file which exists on non-root
1474 A read-only flat-keyed file which exists on non-root cgroups.
1524 A read-only flat-keyed file which exists on non-root cgroups.
1653 Number of restored anonymous pages which have been detected as
1657 Number of restored file pages which have been detected as an
1739 Number of transparent hugepages which were allocated to satisfy
1744 Number of transparent hugepages which were allocated to allow
1749 Number of transparent hugepages which are swapout in one piece
1753 Number of transparent hugepages which were split before swapout.
1785 A read-only nested-keyed file which exists on non-root cgroups.
1810 A read-only single value file which exists on non-root
1817 A read-write single value file which exists on non-root
1826 during regular operation. Compare to memory.swap.max, which
1833 A read-write single value file which exists on non-root cgroups.
1843 A read-write single value file which exists on non-root
1850 A read-only flat-keyed file which exists on non-root cgroups.
1875 A read-only single value file which exists on non-root
1882 A read-write single value file which exists on non-root
1929 more memory. For example, a workload which writes data received from
1941 A memory area is charged to the cgroup which instantiated it and stays
1947 To which cgroup the area will be charged is in-deterministic; however,
1948 over time, the memory area is likely to end up in a cgroup which has
1951 If a cgroup sweeps a considerable amount of memory which is expected
1991 A read-write nested-keyed file which exists only on the root
1995 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
2035 devices which show wide temporary behavior changes - e.g. a
2036 ssd which accepts writes at the line speed for a while and
2046 A read-write nested-keyed file which exists only on the root
2050 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
2088 A read-write flat-keyed file which exists on non-root cgroups.
2108 A read-write nested-keyed file which exists on non-root
2165 maintained for and the io controller defines the io domain which
2176 which affects how cgroup ownership is tracked. Memory is tracked per
2182 which are associated with different cgroups than the one the inode is
2199 The sysctl knobs which affect writeback behavior are applied to cgroup
2361 The number of tasks in a cgroup can be exhausted in ways which other
2374 A read-write single value file which exists on non-root
2380 A read-only single value file which exists on non-root cgroups.
2386 A read-only single value file which exists on non-root cgroups.
2392 A read-only flat-keyed file which exists on non-root cgroups. Unless
2433 A read-write multiple values file which exists on non-root
2455 A read-only multiple values file which exists on all
2472 A read-write multiple values file which exists on non-root
2506 A read-only multiple values file which exists on all
2522 A read-write multiple values file which exists on non-root
2533 "cpuset.cpus.exclusive.effective" which may be different
2556 A read-only multiple values file which exists on all non-root
2576 A read-write single value file which exists on non-root
2702 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2755 which does not have to be equal to the system page size, the units are always bytes.
2811 A read-only flat-keyed file which exists on non-root cgroups.
2830 mechanism for the scalar resources which cannot be abstracted like the other
2894 A read-only flat-keyed file which exists on non-root cgroups. The
2911 A miscellaneous scalar resource is charged to the cgroup in which it is used
3011 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
3134 selective disabling of cgroup writeback support which is helpful when
3173 type controllers such as freezer which can be useful in all
3181 In practice, these issues heavily limited which controllers could be
3194 There was no limit on how many hierarchies there might be, which meant
3197 in length, which made it highly awkward to manipulate and led to
3198 addition of controllers which existed only to identify membership,
3199 which in turn exacerbated the original problem of proliferating number
3208 In most use cases, putting controllers on hierarchies which are
3230 the application which owns the target process.
3232 cgroup v1 had an ambiguously defined delegation model which got abused
3248 cgroup controllers implemented a number of knobs which would never be
3251 knobs which were not properly abstracted or refined and directly
3265 cgroup v1 allowed threads to be in any cgroups which created an
3277 wasn't obvious or universal, and there were various other knobs which
3284 always added an extra layer of nesting which wouldn't be necessary
3291 knobs to tailor the behavior to specific workloads which would have
3299 This clearly is a problem which needs to be addressed from cgroup core
3354 effective low, which makes delegation of subtrees possible. It also