Lines Matching full:which
118 although there are utility controllers which serve purposes other than
131 processes which belong to the cgroups consisting the inclusive
150 controllers which support v2 and are not bound to a v1 hierarchy are
152 Controllers which are not in active use in the v2 hierarchy can be
257 Initially, only the root cgroup exists to which all processes belong.
264 "cgroup.procs". When read, it lists the PIDs of all processes which
282 A cgroup which doesn't have any children or live processes can be
283 destroyed by removing the directory. Note that a cgroup which doesn't
312 process belong to the same cgroup, which also serves as the resource
313 domain to host resource consumptions which are not specific to a
317 Controllers which support thread mode are called threaded controllers.
318 The ones which don't are called domain controllers.
323 of a threaded subtree, that is, the nearest ancestor which is not
335 can't have populated child cgroups which aren't threaded. Because the
340 "cgroup.type" file which indicates whether the cgroup is a normal
341 domain, a domain which is serving as the domain of a threaded subtree,
365 C is created as a domain but isn't connected to a parent which can
368 these cases. Operations which fail due to invalid topology use
396 threads in the cgroup and its descendants. All consumptions which
415 Each non-root cgroup has a "cgroup.events" file which contains
450 Each cgroup has a "cgroup.controllers" file which lists all
461 Only controllers which are listed in "cgroup.controllers" can be
485 controller interface files - anything which doesn't start with
495 can only contain controllers which are enabled in the parent's
506 only domain cgroups which don't contain any processes can have domain
510 of the hierarchy which has it enabled, processes are always only on
515 processes and anonymous resource consumption which can't be associated
595 Let's also say U0 wants to write the PID of a process which is
604 namespace of the process which is attempting the migration. If either
632 directory and it is possible to create children cgroups which collide
640 start or end with terms which are often used in categorizing workloads
660 weight against the sum. As only children which can make use of the
686 Limits are in the range [0, max] and defaults to "max", which is noop.
703 soft boundaries. Protections can also be over-committed in which case
707 Protections are in the range [0, max] and defaults to 0, which is
726 Allocations are in the range [0, max] and defaults to 0, which is no
820 For example, a setting which is keyed by major:minor device numbers
846 - For events which are not very high frequency, an interface file
847 "events" should be created which lists event key value pairs.
858 A read-write single value file which exists on non-root
861 When read, it indicates the current type of the cgroup, which
866 - "domain threaded" : A threaded domain cgroup which is
869 - "domain invalid" : A cgroup which is in an invalid state.
873 - "threaded" : A threaded cgroup which is a member of a
880 A read-write new-line separated values file which exists on
883 When read, it lists the PIDs of all processes which belong to
906 A read-write new-line separated values file which exists on
909 When read, it lists the TIDs of all threads which belong to
931 A read-only space separated values file which exists on all
938 A read-write space separated values file which exists on all
942 which are enabled to control resource distribution from the
953 A read-only flat-keyed file which exists on non-root cgroups.
987 in dying state for some time undefined time (which can depend
994 limits, which were active at the moment of cgroup deletion.
1005 A read-write single value file which exists on non-root cgroups.
1031 A write-only single value file which exists in non-root cgroups.
1059 deep level of the hierarchy, in which case this control attribute can
1082 base and it does not account for the frequency at which tasks are executed.
1084 cpufreq governor about the minimum desired frequency which should always be
1085 provided by a CPU, as well as the maximum desired frequency, which should not
1126 It always reports the following three stats, which account for all the
1133 and the following five when the controller is enabled, which account for
1143 A read-write single value file which exists on non-root
1157 A read-write single value file which exists on non-root
1173 A read-write two value file which exists on non-root cgroups.
1180 which indicates that the group may consume up to $MAX in each
1187 A read-write single value file which exists on non-root
1203 A read-write single value file which exists on non-root cgroups.
1221 A read-write single value file which exists on non-root cgroups.
1235 A read-write single value file which exists on non-root cgroups.
1272 All memory amounts are in bytes. If a value which is not aligned to
1277 A read-only single value file which exists on non-root
1284 A read-write single value file which exists on non-root
1310 A read-write single value file which exists on non-root
1333 A read-write single value file which exists on non-root
1359 A read-write single value file which exists on non-root
1388 A write-only nested-keyed file which exists for all cgroups.
1423 A read-write single value file which exists on non-root cgroups.
1433 A read-write single value file which exists on non-root
1451 A read-only flat-keyed file which exists on non-root cgroups.
1501 A read-only flat-keyed file which exists on non-root cgroups.
1630 Number of restored anonymous pages which have been detected as
1634 Number of restored file pages which have been detected as an
1716 Number of transparent hugepages which were allocated to satisfy
1721 Number of transparent hugepages which were allocated to allow
1726 Number of transparent hugepages which are swapout in one piece
1730 Number of transparent hugepages which were split before swapout.
1762 A read-only nested-keyed file which exists on non-root cgroups.
1787 A read-only single value file which exists on non-root
1794 A read-write single value file which exists on non-root
1803 during regular operation. Compare to memory.swap.max, which
1810 A read-write single value file which exists on non-root cgroups.
1820 A read-write single value file which exists on non-root
1827 A read-only flat-keyed file which exists on non-root cgroups.
1852 A read-only single value file which exists on non-root
1859 A read-write single value file which exists on non-root
1906 more memory. For example, a workload which writes data received from
1918 A memory area is charged to the cgroup which instantiated it and stays
1924 To which cgroup the area will be charged is in-deterministic; however,
1925 over time, the memory area is likely to end up in a cgroup which has
1928 If a cgroup sweeps a considerable amount of memory which is expected
1968 A read-write nested-keyed file which exists only on the root
1972 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
2012 devices which show wide temporary behavior changes - e.g. a
2013 ssd which accepts writes at the line speed for a while and
2023 A read-write nested-keyed file which exists only on the root
2027 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
2065 A read-write flat-keyed file which exists on non-root cgroups.
2085 A read-write nested-keyed file which exists on non-root
2142 maintained for and the io controller defines the io domain which
2153 which affects how cgroup ownership is tracked. Memory is tracked per
2159 which are associated with different cgroups than the one the inode is
2176 The sysctl knobs which affect writeback behavior are applied to cgroup
2338 The number of tasks in a cgroup can be exhausted in ways which other
2351 A read-write single value file which exists on non-root
2357 A read-only single value file which exists on non-root cgroups.
2363 A read-only single value file which exists on non-root cgroups.
2369 A read-only flat-keyed file which exists on non-root cgroups. Unless
2410 A read-write multiple values file which exists on non-root
2432 A read-only multiple values file which exists on all
2449 A read-write multiple values file which exists on non-root
2483 A read-only multiple values file which exists on all
2499 A read-write multiple values file which exists on non-root
2510 "cpuset.cpus.exclusive.effective" which may be different
2533 A read-only multiple values file which exists on all non-root
2553 A read-write single value file which exists on non-root
2679 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2732 which does not have to be equal to the system page size, the units are always bytes.
2788 A read-only flat-keyed file which exists on non-root cgroups.
2807 mechanism for the scalar resources which cannot be abstracted like the other
2871 A read-only flat-keyed file which exists on non-root cgroups. The
2888 A miscellaneous scalar resource is charged to the cgroup in which it is used
2988 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
3111 selective disabling of cgroup writeback support which is helpful when
3150 type controllers such as freezer which can be useful in all
3158 In practice, these issues heavily limited which controllers could be
3171 There was no limit on how many hierarchies there might be, which meant
3174 in length, which made it highly awkward to manipulate and led to
3175 addition of controllers which existed only to identify membership,
3176 which in turn exacerbated the original problem of proliferating number
3185 In most use cases, putting controllers on hierarchies which are
3207 the application which owns the target process.
3209 cgroup v1 had an ambiguously defined delegation model which got abused
3225 cgroup controllers implemented a number of knobs which would never be
3228 knobs which were not properly abstracted or refined and directly
3242 cgroup v1 allowed threads to be in any cgroups which created an
3254 wasn't obvious or universal, and there were various other knobs which
3261 always added an extra layer of nesting which wouldn't be necessary
3268 knobs to tailor the behavior to specific workloads which would have
3276 This clearly is a problem which needs to be addressed from cgroup core
3331 effective low, which makes delegation of subtrees possible. It also