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
629 Limits are in the range [0, max] and defaults to "max", which is noop.
645 soft boundaries. Protections can also be over-committed in which case
649 Protections are in the range [0, max] and defaults to 0, which is
668 Allocations are in the range [0, max] and defaults to 0, which is no
762 For example, a setting which is keyed by major:minor device numbers
788 - For events which are not very high frequency, an interface file
789 "events" should be created which lists event key value pairs.
800 A read-write single value file which exists on non-root
803 When read, it indicates the current type of the cgroup, which
808 - "domain threaded" : A threaded domain cgroup which is
811 - "domain invalid" : A cgroup which is in an invalid state.
815 - "threaded" : A threaded cgroup which is a member of a
822 A read-write new-line separated values file which exists on
825 When read, it lists the PIDs of all processes which belong to
848 A read-write new-line separated values file which exists on
851 When read, it lists the TIDs of all threads which belong to
873 A read-only space separated values file which exists on all
880 A read-write space separated values file which exists on all
884 which are enabled to control resource distribution from the
895 A read-only flat-keyed file which exists on non-root cgroups.
929 in dying state for some time undefined time (which can depend
936 limits, which were active at the moment of cgroup deletion.
939 A read-write single value file which exists on non-root cgroups.
965 A write-only single value file which exists in non-root cgroups.
993 deep level of the hierarchy, in which case this control attribute can
1016 base and it does not account for the frequency at which tasks are executed.
1018 cpufreq governor about the minimum desired frequency which should always be
1019 provided by a CPU, as well as the maximum desired frequency, which should not
1054 A read-write single value file which exists on non-root
1060 A read-write single value file which exists on non-root
1072 A read-write two value file which exists on non-root cgroups.
1079 which indicates that the group may consume upto $MAX in each
1084 A read-write single value file which exists on non-root
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.
1149 All memory amounts are in bytes. If a value which is not aligned to
1154 A read-only single value file which exists on non-root
1161 A read-write single value file which exists on non-root
1187 A read-write single value file which exists on non-root
1210 A read-write single value file which exists on non-root
1222 A read-write single value file which exists on non-root
1243 A write-only nested-keyed file which exists for all cgroups.
1271 A read-only single value file which exists on non-root
1278 A read-write single value file which exists on non-root
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.
1469 Number of restored anonymous pages which have been detected as
1473 Number of restored file pages which have been detected as an
1519 Number of transparent hugepages which were allocated to satisfy
1524 Number of transparent hugepages which were allocated to allow
1529 A read-only nested-keyed file which exists on non-root cgroups.
1554 A read-only single value file which exists on non-root
1561 A read-write single value file which exists on non-root
1570 during regular operation. Compare to memory.swap.max, which
1577 A read-write single value file which exists on non-root
1584 A read-only flat-keyed file which exists on non-root cgroups.
1609 A read-only single value file which exists on non-root
1616 A read-write single value file which exists on non-root
1645 more memory. For example, a workload which writes data received from
1657 A memory area is charged to the cgroup which instantiated it and stays
1663 To which cgroup the area will be charged is in-deterministic; however,
1664 over time, the memory area is likely to end up in a cgroup which has
1667 If a cgroup sweeps a considerable amount of memory which is expected
1707 A read-write nested-keyed file which exists only on the root
1711 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1751 devices which show wide temporary behavior changes - e.g. a
1752 ssd which accepts writes at the line speed for a while and
1762 A read-write nested-keyed file which exists only on the root
1766 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1804 A read-write flat-keyed file which exists on non-root cgroups.
1824 A read-write nested-keyed file which exists on non-root
1881 maintained for and the io controller defines the io domain which
1892 which affects how cgroup ownership is tracked. Memory is tracked per
1898 which are associated with different cgroups than the one the inode is
1915 The sysctl knobs which affect writeback behavior are applied to cgroup
2069 The number of tasks in a cgroup can be exhausted in ways which other
2082 A read-write single value file which exists on non-root
2088 A read-only single value file which exists on all cgroups.
2121 A read-write multiple values file which exists on non-root
2143 A read-only multiple values file which exists on all
2160 A read-write multiple values file which exists on non-root
2194 A read-only multiple values file which exists on all
2210 A read-write single value file which exists on non-root
2320 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2386 A read-only flat-keyed file which exists on non-root cgroups.
2405 mechanism for the scalar resources which cannot be abstracted like the other
2460 A read-only flat-keyed file which exists on non-root cgroups. The
2472 A miscellaneous scalar resource is charged to the cgroup in which it is used
2572 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2695 selective disabling of cgroup writeback support which is helpful when
2734 type controllers such as freezer which can be useful in all
2742 In practice, these issues heavily limited which controllers could be
2755 There was no limit on how many hierarchies there might be, which meant
2758 in length, which made it highly awkward to manipulate and led to
2759 addition of controllers which existed only to identify membership,
2760 which in turn exacerbated the original problem of proliferating number
2769 In most use cases, putting controllers on hierarchies which are
2791 the application which owns the target process.
2793 cgroup v1 had an ambiguously defined delegation model which got abused
2809 cgroup controllers implemented a number of knobs which would never be
2812 knobs which were not properly abstracted or refined and directly
2826 cgroup v1 allowed threads to be in any cgroups which created an
2838 wasn't obvious or universal, and there were various other knobs which
2845 always added an extra layer of nesting which wouldn't be necessary
2852 knobs to tailor the behavior to specific workloads which would have
2860 This clearly is a problem which needs to be addressed from cgroup core
2915 effective low, which makes delegation of subtrees possible. It also