Lines Matching full:which
111 although there are utility controllers which serve purposes other than
124 processes which belong to the cgroups consisting the inclusive
143 controllers which support v2 and are not bound to a v1 hierarchy are
145 Controllers which are not in active use in the v2 hierarchy can be
209 Initially, only the root cgroup exists to which all processes belong.
216 "cgroup.procs". When read, it lists the PIDs of all processes which
234 A cgroup which doesn't have any children or live processes can be
235 destroyed by removing the directory. Note that a cgroup which doesn't
264 process belong to the same cgroup, which also serves as the resource
265 domain to host resource consumptions which are not specific to a
269 Controllers which support thread mode are called threaded controllers.
270 The ones which don't are called domain controllers.
275 of a threaded subtree, that is, the nearest ancestor which is not
287 can't have populated child cgroups which aren't threaded. Because the
292 "cgroup.type" file which indicates whether the cgroup is a normal
293 domain, a domain which is serving as the domain of a threaded subtree,
317 C is created as a domain but isn't connected to a parent which can
320 these cases. Operations which fail due to invalid topology use
348 threads in the cgroup and its descendants. All consumptions which
360 Each non-root cgroup has a "cgroup.events" file which contains
386 Each cgroup has a "cgroup.controllers" file which lists all
397 Only controllers which are listed in "cgroup.controllers" can be
421 controller interface files - anything which doesn't start with
431 can only contain controllers which are enabled in the parent's
442 only domain cgroups which don't contain any processes can have domain
446 of the hierarchy which has it enabled, processes are always only on
451 processes and anonymous resource consumption which can't be associated
529 Let's also say U0 wants to write the PID of a process which is
538 namespace of the process which is attempting the migration. If either
566 directory and it is possible to create children cgroups which collide
574 start or end with terms which are often used in categorizing workloads
594 weight against the sum. As only children which can make use of the
618 Limits are in the range [0, max] and defaults to "max", which is noop.
634 soft boundaries. Protections can also be over-committed in which case
638 Protections are in the range [0, max] and defaults to 0, which is
657 Allocations are in the range [0, max] and defaults to 0, which is no
751 For example, a setting which is keyed by major:minor device numbers
777 - For events which are not very high frequency, an interface file
778 "events" should be created which lists event key value pairs.
790 A read-write single value file which exists on non-root
793 When read, it indicates the current type of the cgroup, which
798 - "domain threaded" : A threaded domain cgroup which is
801 - "domain invalid" : A cgroup which is in an invalid state.
805 - "threaded" : A threaded cgroup which is a member of a
812 A read-write new-line separated values file which exists on
815 When read, it lists the PIDs of all processes which belong to
838 A read-write new-line separated values file which exists on
841 When read, it lists the TIDs of all threads which belong to
863 A read-only space separated values file which exists on all
870 A read-write space separated values file which exists on all
874 which are enabled to control resource distribution from the
885 A read-only flat-keyed file which exists on non-root cgroups.
919 in dying state for some time undefined time (which can depend
926 limits, which were active at the moment of cgroup deletion.
929 A read-write single value file which exists on non-root cgroups.
966 base and it does not account for the frequency at which tasks are executed.
968 cpufreq governor about the minimum desired frequency which should always be
969 provided by a CPU, as well as the maximum desired frequency, which should not
1002 A read-write single value file which exists on non-root
1008 A read-write single value file which exists on non-root
1020 A read-write two value file which exists on non-root cgroups.
1027 which indicates that the group may consume upto $MAX in each
1032 A read-only nested-key file which exists on non-root cgroups.
1038 A read-write single value file which exists on non-root cgroups.
1053 A read-write single value file which exists on non-root cgroups.
1091 All memory amounts are in bytes. If a value which is not aligned to
1096 A read-only single value file which exists on non-root
1103 A read-write single value file which exists on non-root
1129 A read-write single value file which exists on non-root
1152 A read-write single value file which exists on non-root
1164 A read-write single value file which exists on non-root
1185 A read-write single value file which exists on non-root
1203 A read-only flat-keyed file which exists on non-root cgroups.
1250 A read-only flat-keyed file which exists on non-root cgroups.
1339 Number of restored anonymous pages which have been detected as
1343 Number of restored file pages which have been detected as an
1377 Number of transparent hugepages which were allocated to satisfy
1382 Number of transparent hugepages which were allocated to allow
1387 A read-only nested-keyed file which exists on non-root cgroups.
1412 A read-only single value file which exists on non-root
1419 A read-write single value file which exists on non-root
1428 during regular operation. Compare to memory.swap.max, which
1435 A read-write single value file which exists on non-root
1442 A read-only flat-keyed file which exists on non-root cgroups.
1467 A read-only nested-key file which exists on non-root cgroups.
1488 more memory. For example, a workload which writes data received from
1500 A memory area is charged to the cgroup which instantiated it and stays
1506 To which cgroup the area will be charged is in-deterministic; however,
1507 over time, the memory area is likely to end up in a cgroup which has
1510 If a cgroup sweeps a considerable amount of memory which is expected
1554 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1594 devices which show wide temporary behavior changes - e.g. a
1595 ssd which accepts writes at the line speed for a while and
1609 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1647 A read-write flat-keyed file which exists on non-root cgroups.
1667 A read-write nested-keyed file which exists on non-root
1706 A read-only nested-key file which exists on non-root cgroups.
1724 maintained for and the io controller defines the io domain which
1735 which affects how cgroup ownership is tracked. Memory is tracked per
1741 which are associated with different cgroups than the one the inode is
1758 The sysctl knobs which affect writeback behavior are applied to cgroup
1858 The number of tasks in a cgroup can be exhausted in ways which other
1871 A read-write single value file which exists on non-root
1877 A read-only single value file which exists on all cgroups.
1910 A read-write multiple values file which exists on non-root
1932 A read-only multiple values file which exists on all
1949 A read-write multiple values file which exists on non-root
1972 A read-only multiple values file which exists on all
1988 A read-write single value file which exists on non-root
2076 structure, which describes the device access attempt: access type
2142 A read-only flat-keyed file which exists on non-root cgroups.
2247 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2370 selective disabling of cgroup writeback support which is helpful when
2409 type controllers such as freezer which can be useful in all
2417 In practice, these issues heavily limited which controllers could be
2430 There was no limit on how many hierarchies there might be, which meant
2433 in length, which made it highly awkward to manipulate and led to
2434 addition of controllers which existed only to identify membership,
2435 which in turn exacerbated the original problem of proliferating number
2444 In most use cases, putting controllers on hierarchies which are
2466 the application which owns the target process.
2468 cgroup v1 had an ambiguously defined delegation model which got abused
2484 cgroup controllers implemented a number of knobs which would never be
2487 knobs which were not properly abstracted or refined and directly
2501 cgroup v1 allowed threads to be in any cgroups which created an
2513 wasn't obvious or universal, and there were various other knobs which
2520 always added an extra layer of nesting which wouldn't be necessary
2527 knobs to tailor the behavior to specific workloads which would have
2535 This clearly is a problem which needs to be addressed from cgroup core
2590 effective low, which makes delegation of subtrees possible. It also