Lines Matching full:which
117 although there are utility controllers which serve purposes other than
130 processes which belong to the cgroups consisting the inclusive
149 controllers which support v2 and are not bound to a v1 hierarchy are
151 Controllers which are not in active use in the v2 hierarchy can be
220 Initially, only the root cgroup exists to which all processes belong.
227 "cgroup.procs". When read, it lists the PIDs of all processes which
245 A cgroup which doesn't have any children or live processes can be
246 destroyed by removing the directory. Note that a cgroup which doesn't
275 process belong to the same cgroup, which also serves as the resource
276 domain to host resource consumptions which are not specific to a
280 Controllers which support thread mode are called threaded controllers.
281 The ones which don't are called domain controllers.
286 of a threaded subtree, that is, the nearest ancestor which is not
298 can't have populated child cgroups which aren't threaded. Because the
303 "cgroup.type" file which indicates whether the cgroup is a normal
304 domain, a domain which is serving as the domain of a threaded subtree,
328 C is created as a domain but isn't connected to a parent which can
331 these cases. Operations which fail due to invalid topology use
359 threads in the cgroup and its descendants. All consumptions which
371 Each non-root cgroup has a "cgroup.events" file which contains
397 Each cgroup has a "cgroup.controllers" file which lists all
408 Only controllers which are listed in "cgroup.controllers" can be
432 controller interface files - anything which doesn't start with
442 can only contain controllers which are enabled in the parent's
453 only domain cgroups which don't contain any processes can have domain
457 of the hierarchy which has it enabled, processes are always only on
462 processes and anonymous resource consumption which can't be associated
540 Let's also say U0 wants to write the PID of a process which is
549 namespace of the process which is attempting the migration. If either
577 directory and it is possible to create children cgroups which collide
585 start or end with terms which are often used in categorizing workloads
605 weight against the sum. As only children which can make use of the
631 Limits are in the range [0, max] and defaults to "max", which is noop.
648 soft boundaries. Protections can also be over-committed in which case
652 Protections are in the range [0, max] and defaults to 0, which is
671 Allocations are in the range [0, max] and defaults to 0, which is no
765 For example, a setting which is keyed by major:minor device numbers
791 - For events which are not very high frequency, an interface file
792 "events" should be created which lists event key value pairs.
803 A read-write single value file which exists on non-root
806 When read, it indicates the current type of the cgroup, which
811 - "domain threaded" : A threaded domain cgroup which is
814 - "domain invalid" : A cgroup which is in an invalid state.
818 - "threaded" : A threaded cgroup which is a member of a
825 A read-write new-line separated values file which exists on
828 When read, it lists the PIDs of all processes which belong to
851 A read-write new-line separated values file which exists on
854 When read, it lists the TIDs of all threads which belong to
876 A read-only space separated values file which exists on all
883 A read-write space separated values file which exists on all
887 which are enabled to control resource distribution from the
898 A read-only flat-keyed file which exists on non-root cgroups.
932 in dying state for some time undefined time (which can depend
939 limits, which were active at the moment of cgroup deletion.
942 A read-write single value file which exists on non-root cgroups.
968 A write-only single value file which exists in non-root cgroups.
996 deep level of the hierarchy, in which case this control attribute can
1019 base and it does not account for the frequency at which tasks are executed.
1021 cpufreq governor about the minimum desired frequency which should always be
1022 provided by a CPU, as well as the maximum desired frequency, which should not
1057 A read-write single value file which exists on non-root
1063 A read-write single value file which exists on non-root
1075 A read-write two value file which exists on non-root cgroups.
1082 which indicates that the group may consume up to $MAX in each
1087 A read-write single value file which exists on non-root
1099 A read-write single value file which exists on non-root cgroups.
1114 A read-write single value file which exists on non-root cgroups.
1152 All memory amounts are in bytes. If a value which is not aligned to
1157 A read-only single value file which exists on non-root
1164 A read-write single value file which exists on non-root
1190 A read-write single value file which exists on non-root
1213 A read-write single value file which exists on non-root
1227 A read-write single value file which exists on non-root
1244 A write-only nested-keyed file which exists for all cgroups.
1272 A read-only single value file which exists on non-root
1279 A read-write single value file which exists on non-root
1297 A read-only flat-keyed file which exists on non-root cgroups.
1347 A read-only flat-keyed file which exists on non-root cgroups.
1470 Number of restored anonymous pages which have been detected as
1474 Number of restored file pages which have been detected as an
1526 Number of transparent hugepages which were allocated to satisfy
1531 Number of transparent hugepages which were allocated to allow
1536 A read-only nested-keyed file which exists on non-root cgroups.
1561 A read-only single value file which exists on non-root
1568 A read-write single value file which exists on non-root
1577 during regular operation. Compare to memory.swap.max, which
1584 A read-only single value file which exists on non-root
1591 A read-write single value file which exists on non-root
1598 A read-only flat-keyed file which exists on non-root cgroups.
1623 A read-only single value file which exists on non-root
1630 A read-write single value file which exists on non-root
1659 more memory. For example, a workload which writes data received from
1671 A memory area is charged to the cgroup which instantiated it and stays
1677 To which cgroup the area will be charged is in-deterministic; however,
1678 over time, the memory area is likely to end up in a cgroup which has
1681 If a cgroup sweeps a considerable amount of memory which is expected
1721 A read-write nested-keyed file which exists only on the root
1725 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1765 devices which show wide temporary behavior changes - e.g. a
1766 ssd which accepts writes at the line speed for a while and
1776 A read-write nested-keyed file which exists only on the root
1780 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1818 A read-write flat-keyed file which exists on non-root cgroups.
1838 A read-write nested-keyed file which exists on non-root
1895 maintained for and the io controller defines the io domain which
1906 which affects how cgroup ownership is tracked. Memory is tracked per
1912 which are associated with different cgroups than the one the inode is
1929 The sysctl knobs which affect writeback behavior are applied to cgroup
2089 The number of tasks in a cgroup can be exhausted in ways which other
2102 A read-write single value file which exists on non-root
2108 A read-only single value file which exists on all cgroups.
2141 A read-write multiple values file which exists on non-root
2163 A read-only multiple values file which exists on all
2180 A read-write multiple values file which exists on non-root
2214 A read-only multiple values file which exists on all
2230 A read-write single value file which exists on non-root
2340 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2406 A read-only flat-keyed file which exists on non-root cgroups.
2425 mechanism for the scalar resources which cannot be abstracted like the other
2480 A read-only flat-keyed file which exists on non-root cgroups. The
2492 A miscellaneous scalar resource is charged to the cgroup in which it is used
2592 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2715 selective disabling of cgroup writeback support which is helpful when
2754 type controllers such as freezer which can be useful in all
2762 In practice, these issues heavily limited which controllers could be
2775 There was no limit on how many hierarchies there might be, which meant
2778 in length, which made it highly awkward to manipulate and led to
2779 addition of controllers which existed only to identify membership,
2780 which in turn exacerbated the original problem of proliferating number
2789 In most use cases, putting controllers on hierarchies which are
2811 the application which owns the target process.
2813 cgroup v1 had an ambiguously defined delegation model which got abused
2829 cgroup controllers implemented a number of knobs which would never be
2832 knobs which were not properly abstracted or refined and directly
2846 cgroup v1 allowed threads to be in any cgroups which created an
2858 wasn't obvious or universal, and there were various other knobs which
2865 always added an extra layer of nesting which wouldn't be necessary
2872 knobs to tailor the behavior to specific workloads which would have
2880 This clearly is a problem which needs to be addressed from cgroup core
2935 effective low, which makes delegation of subtrees possible. It also