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
249 Initially, only the root cgroup exists to which all processes belong.
256 "cgroup.procs". When read, it lists the PIDs of all processes which
274 A cgroup which doesn't have any children or live processes can be
275 destroyed by removing the directory. Note that a cgroup which doesn't
304 process belong to the same cgroup, which also serves as the resource
305 domain to host resource consumptions which are not specific to a
309 Controllers which support thread mode are called threaded controllers.
310 The ones which don't are called domain controllers.
315 of a threaded subtree, that is, the nearest ancestor which is not
327 can't have populated child cgroups which aren't threaded. Because the
332 "cgroup.type" file which indicates whether the cgroup is a normal
333 domain, a domain which is serving as the domain of a threaded subtree,
357 C is created as a domain but isn't connected to a parent which can
360 these cases. Operations which fail due to invalid topology use
388 threads in the cgroup and its descendants. All consumptions which
407 Each non-root cgroup has a "cgroup.events" file which contains
433 Each cgroup has a "cgroup.controllers" file which lists all
444 Only controllers which are listed in "cgroup.controllers" can be
468 controller interface files - anything which doesn't start with
478 can only contain controllers which are enabled in the parent's
489 only domain cgroups which don't contain any processes can have domain
493 of the hierarchy which has it enabled, processes are always only on
498 processes and anonymous resource consumption which can't be associated
576 Let's also say U0 wants to write the PID of a process which is
585 namespace of the process which is attempting the migration. If either
613 directory and it is possible to create children cgroups which collide
621 start or end with terms which are often used in categorizing workloads
641 weight against the sum. As only children which can make use of the
667 Limits are in the range [0, max] and defaults to "max", which is noop.
684 soft boundaries. Protections can also be over-committed in which case
688 Protections are in the range [0, max] and defaults to 0, which is
707 Allocations are in the range [0, max] and defaults to 0, which is no
801 For example, a setting which is keyed by major:minor device numbers
827 - For events which are not very high frequency, an interface file
828 "events" should be created which lists event key value pairs.
839 A read-write single value file which exists on non-root
842 When read, it indicates the current type of the cgroup, which
847 - "domain threaded" : A threaded domain cgroup which is
850 - "domain invalid" : A cgroup which is in an invalid state.
854 - "threaded" : A threaded cgroup which is a member of a
861 A read-write new-line separated values file which exists on
864 When read, it lists the PIDs of all processes which belong to
887 A read-write new-line separated values file which exists on
890 When read, it lists the TIDs of all threads which belong to
912 A read-only space separated values file which exists on all
919 A read-write space separated values file which exists on all
923 which are enabled to control resource distribution from the
934 A read-only flat-keyed file which exists on non-root cgroups.
968 in dying state for some time undefined time (which can depend
975 limits, which were active at the moment of cgroup deletion.
978 A read-write single value file which exists on non-root cgroups.
1004 A write-only single value file which exists in non-root cgroups.
1032 deep level of the hierarchy, in which case this control attribute can
1055 base and it does not account for the frequency at which tasks are executed.
1057 cpufreq governor about the minimum desired frequency which should always be
1058 provided by a CPU, as well as the maximum desired frequency, which should not
1093 A read-write single value file which exists on non-root
1103 A read-write single value file which exists on non-root
1115 A read-write two value file which exists on non-root cgroups.
1122 which indicates that the group may consume up to $MAX in each
1127 A read-write single value file which exists on non-root
1139 A read-write single value file which exists on non-root cgroups.
1154 A read-write single value file which exists on non-root cgroups.
1165 A read-write single value file which exists on non-root cgroups.
1202 All memory amounts are in bytes. If a value which is not aligned to
1207 A read-only single value file which exists on non-root
1214 A read-write single value file which exists on non-root
1240 A read-write single value file which exists on non-root
1263 A read-write single value file which exists on non-root
1277 A read-write single value file which exists on non-root
1294 A write-only nested-keyed file which exists for all cgroups.
1322 A read-only single value file which exists on non-root
1329 A read-write single value file which exists on non-root
1347 A read-only flat-keyed file which exists on non-root cgroups.
1397 A read-only flat-keyed file which exists on non-root cgroups.
1520 Number of restored anonymous pages which have been detected as
1524 Number of restored file pages which have been detected as an
1576 Number of transparent hugepages which were allocated to satisfy
1581 Number of transparent hugepages which were allocated to allow
1586 Number of transparent hugepages which are swapout in one piece
1590 Number of transparent hugepages which were split before swapout.
1595 A read-only nested-keyed file which exists on non-root cgroups.
1620 A read-only single value file which exists on non-root
1627 A read-write single value file which exists on non-root
1636 during regular operation. Compare to memory.swap.max, which
1643 A read-only single value file which exists on non-root
1650 A read-write single value file which exists on non-root
1657 A read-only flat-keyed file which exists on non-root cgroups.
1682 A read-only single value file which exists on non-root
1689 A read-write single value file which exists on non-root
1733 more memory. For example, a workload which writes data received from
1745 A memory area is charged to the cgroup which instantiated it and stays
1751 To which cgroup the area will be charged is in-deterministic; however,
1752 over time, the memory area is likely to end up in a cgroup which has
1755 If a cgroup sweeps a considerable amount of memory which is expected
1795 A read-write nested-keyed file which exists only on the root
1799 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1839 devices which show wide temporary behavior changes - e.g. a
1840 ssd which accepts writes at the line speed for a while and
1850 A read-write nested-keyed file which exists only on the root
1854 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1892 A read-write flat-keyed file which exists on non-root cgroups.
1912 A read-write nested-keyed file which exists on non-root
1969 maintained for and the io controller defines the io domain which
1980 which affects how cgroup ownership is tracked. Memory is tracked per
1986 which are associated with different cgroups than the one the inode is
2003 The sysctl knobs which affect writeback behavior are applied to cgroup
2165 The number of tasks in a cgroup can be exhausted in ways which other
2178 A read-write single value file which exists on non-root
2184 A read-only single value file which exists on all cgroups.
2217 A read-write multiple values file which exists on non-root
2239 A read-only multiple values file which exists on all
2256 A read-write multiple values file which exists on non-root
2290 A read-only multiple values file which exists on all
2306 A read-write multiple values file which exists on non-root
2317 "cpuset.cpus.exclusive.effective" which may be different
2336 A read-only multiple values file which exists on all non-root
2356 A read-write single value file which exists on non-root
2482 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2548 A read-only flat-keyed file which exists on non-root cgroups.
2567 mechanism for the scalar resources which cannot be abstracted like the other
2622 A read-only flat-keyed file which exists on non-root cgroups. The
2634 A miscellaneous scalar resource is charged to the cgroup in which it is used
2734 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2857 selective disabling of cgroup writeback support which is helpful when
2896 type controllers such as freezer which can be useful in all
2904 In practice, these issues heavily limited which controllers could be
2917 There was no limit on how many hierarchies there might be, which meant
2920 in length, which made it highly awkward to manipulate and led to
2921 addition of controllers which existed only to identify membership,
2922 which in turn exacerbated the original problem of proliferating number
2931 In most use cases, putting controllers on hierarchies which are
2953 the application which owns the target process.
2955 cgroup v1 had an ambiguously defined delegation model which got abused
2971 cgroup controllers implemented a number of knobs which would never be
2974 knobs which were not properly abstracted or refined and directly
2988 cgroup v1 allowed threads to be in any cgroups which created an
3000 wasn't obvious or universal, and there were various other knobs which
3007 always added an extra layer of nesting which wouldn't be necessary
3014 knobs to tailor the behavior to specific workloads which would have
3022 This clearly is a problem which needs to be addressed from cgroup core
3077 effective low, which makes delegation of subtrees possible. It also