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
212 Initially, only the root cgroup exists to which all processes belong.
219 "cgroup.procs". When read, it lists the PIDs of all processes which
237 A cgroup which doesn't have any children or live processes can be
238 destroyed by removing the directory. Note that a cgroup which doesn't
267 process belong to the same cgroup, which also serves as the resource
268 domain to host resource consumptions which are not specific to a
272 Controllers which support thread mode are called threaded controllers.
273 The ones which don't are called domain controllers.
278 of a threaded subtree, that is, the nearest ancestor which is not
290 can't have populated child cgroups which aren't threaded. Because the
295 "cgroup.type" file which indicates whether the cgroup is a normal
296 domain, a domain which is serving as the domain of a threaded subtree,
320 C is created as a domain but isn't connected to a parent which can
323 these cases. Operations which fail due to invalid topology use
351 threads in the cgroup and its descendants. All consumptions which
363 Each non-root cgroup has a "cgroup.events" file which contains
389 Each cgroup has a "cgroup.controllers" file which lists all
400 Only controllers which are listed in "cgroup.controllers" can be
424 controller interface files - anything which doesn't start with
434 can only contain controllers which are enabled in the parent's
445 only domain cgroups which don't contain any processes can have domain
449 of the hierarchy which has it enabled, processes are always only on
454 processes and anonymous resource consumption which can't be associated
532 Let's also say U0 wants to write the PID of a process which is
541 namespace of the process which is attempting the migration. If either
569 directory and it is possible to create children cgroups which collide
577 start or end with terms which are often used in categorizing workloads
597 weight against the sum. As only children which can make use of the
621 Limits are in the range [0, max] and defaults to "max", which is noop.
637 soft boundaries. Protections can also be over-committed in which case
641 Protections are in the range [0, max] and defaults to 0, which is
660 Allocations are in the range [0, max] and defaults to 0, which is no
754 For example, a setting which is keyed by major:minor device numbers
780 - For events which are not very high frequency, an interface file
781 "events" should be created which lists event key value pairs.
792 A read-write single value file which exists on non-root
795 When read, it indicates the current type of the cgroup, which
800 - "domain threaded" : A threaded domain cgroup which is
803 - "domain invalid" : A cgroup which is in an invalid state.
807 - "threaded" : A threaded cgroup which is a member of a
814 A read-write new-line separated values file which exists on
817 When read, it lists the PIDs of all processes which belong to
840 A read-write new-line separated values file which exists on
843 When read, it lists the TIDs of all threads which belong to
865 A read-only space separated values file which exists on all
872 A read-write space separated values file which exists on all
876 which are enabled to control resource distribution from the
887 A read-only flat-keyed file which exists on non-root cgroups.
921 in dying state for some time undefined time (which can depend
928 limits, which were active at the moment of cgroup deletion.
931 A read-write single value file which exists on non-root cgroups.
957 A write-only single value file which exists in non-root cgroups.
985 base and it does not account for the frequency at which tasks are executed.
987 cpufreq governor about the minimum desired frequency which should always be
988 provided by a CPU, as well as the maximum desired frequency, which should not
1021 A read-write single value file which exists on non-root
1027 A read-write single value file which exists on non-root
1039 A read-write two value file which exists on non-root cgroups.
1046 which indicates that the group may consume upto $MAX in each
1057 A read-write single value file which exists on non-root cgroups.
1072 A read-write single value file which exists on non-root cgroups.
1110 All memory amounts are in bytes. If a value which is not aligned to
1115 A read-only single value file which exists on non-root
1122 A read-write single value file which exists on non-root
1148 A read-write single value file which exists on non-root
1171 A read-write single value file which exists on non-root
1183 A read-write single value file which exists on non-root
1204 A read-write single value file which exists on non-root
1222 A read-only flat-keyed file which exists on non-root cgroups.
1269 A read-only flat-keyed file which exists on non-root cgroups.
1373 Number of restored anonymous pages which have been detected as
1377 Number of restored file pages which have been detected as an
1411 Number of transparent hugepages which were allocated to satisfy
1416 Number of transparent hugepages which were allocated to allow
1421 A read-only nested-keyed file which exists on non-root cgroups.
1446 A read-only single value file which exists on non-root
1453 A read-write single value file which exists on non-root
1462 during regular operation. Compare to memory.swap.max, which
1469 A read-write single value file which exists on non-root
1476 A read-only flat-keyed file which exists on non-root cgroups.
1522 more memory. For example, a workload which writes data received from
1534 A memory area is charged to the cgroup which instantiated it and stays
1540 To which cgroup the area will be charged is in-deterministic; however,
1541 over time, the memory area is likely to end up in a cgroup which has
1544 If a cgroup sweeps a considerable amount of memory which is expected
1584 A read-write nested-keyed file which exists only on the root
1588 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1628 devices which show wide temporary behavior changes - e.g. a
1629 ssd which accepts writes at the line speed for a while and
1639 A read-write nested-keyed file which exists only on the root
1643 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1681 A read-write flat-keyed file which exists on non-root cgroups.
1701 A read-write nested-keyed file which exists on non-root
1758 maintained for and the io controller defines the io domain which
1769 which affects how cgroup ownership is tracked. Memory is tracked per
1775 which are associated with different cgroups than the one the inode is
1792 The sysctl knobs which affect writeback behavior are applied to cgroup
1946 The number of tasks in a cgroup can be exhausted in ways which other
1959 A read-write single value file which exists on non-root
1965 A read-only single value file which exists on all cgroups.
1998 A read-write multiple values file which exists on non-root
2020 A read-only multiple values file which exists on all
2037 A read-write multiple values file which exists on non-root
2071 A read-only multiple values file which exists on all
2087 A read-write single value file which exists on non-root
2179 bpf_cgroup_dev_ctx structure, which describes the device access attempt:
2245 A read-only flat-keyed file which exists on non-root cgroups.
2259 mechanism for the scalar resources which cannot be abstracted like the other
2316 A miscellaneous scalar resource is charged to the cgroup in which it is used
2416 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2539 selective disabling of cgroup writeback support which is helpful when
2578 type controllers such as freezer which can be useful in all
2586 In practice, these issues heavily limited which controllers could be
2599 There was no limit on how many hierarchies there might be, which meant
2602 in length, which made it highly awkward to manipulate and led to
2603 addition of controllers which existed only to identify membership,
2604 which in turn exacerbated the original problem of proliferating number
2613 In most use cases, putting controllers on hierarchies which are
2635 the application which owns the target process.
2637 cgroup v1 had an ambiguously defined delegation model which got abused
2653 cgroup controllers implemented a number of knobs which would never be
2656 knobs which were not properly abstracted or refined and directly
2670 cgroup v1 allowed threads to be in any cgroups which created an
2682 wasn't obvious or universal, and there were various other knobs which
2689 always added an extra layer of nesting which wouldn't be necessary
2696 knobs to tailor the behavior to specific workloads which would have
2704 This clearly is a problem which needs to be addressed from cgroup core
2759 effective low, which makes delegation of subtrees possible. It also