Lines Matching full:which
109 although there are utility controllers which serve purposes other than
122 processes which belong to the cgroups consisting the inclusive
141 controllers which support v2 and are not bound to a v1 hierarchy are
143 Controllers which are not in active use in the v2 hierarchy can be
196 Initially, only the root cgroup exists to which all processes belong.
203 "cgroup.procs". When read, it lists the PIDs of all processes which
221 A cgroup which doesn't have any children or live processes can be
222 destroyed by removing the directory. Note that a cgroup which doesn't
251 process belong to the same cgroup, which also serves as the resource
252 domain to host resource consumptions which are not specific to a
256 Controllers which support thread mode are called threaded controllers.
257 The ones which don't are called domain controllers.
262 of a threaded subtree, that is, the nearest ancestor which is not
274 can't have populated child cgroups which aren't threaded. Because the
279 "cgroup.type" file which indicates whether the cgroup is a normal
280 domain, a domain which is serving as the domain of a threaded subtree,
304 C is created as a domain but isn't connected to a parent which can
307 these cases. Operations which fail due to invalid topology use
335 threads in the cgroup and its descendants. All consumptions which
347 Each non-root cgroup has a "cgroup.events" file which contains
373 Each cgroup has a "cgroup.controllers" file which lists all
384 Only controllers which are listed in "cgroup.controllers" can be
408 controller interface files - anything which doesn't start with
418 can only contain controllers which are enabled in the parent's
429 only domain cgroups which don't contain any processes can have domain
433 of the hierarchy which has it enabled, processes are always only on
438 processes and anonymous resource consumption which can't be associated
516 Let's also say U0 wants to write the PID of a process which is
525 namespace of the process which is attempting the migration. If either
553 directory and it is possible to create children cgroups which collide
561 start or end with terms which are often used in categorizing workloads
581 weight against the sum. As only children which can make use of the
605 Limits are in the range [0, max] and defaults to "max", which is noop.
621 soft boundaries. Protections can also be over-committed in which case
625 Protections are in the range [0, max] and defaults to 0, which is
644 Allocations are in the range [0, max] and defaults to 0, which is no
705 informational files on the root cgroup which end up showing global
740 For example, a setting which is keyed by major:minor device numbers
766 - For events which are not very high frequency, an interface file
767 "events" should be created which lists event key value pairs.
779 A read-write single value file which exists on non-root
782 When read, it indicates the current type of the cgroup, which
787 - "domain threaded" : A threaded domain cgroup which is
790 - "domain invalid" : A cgroup which is in an invalid state.
794 - "threaded" : A threaded cgroup which is a member of a
801 A read-write new-line separated values file which exists on
804 When read, it lists the PIDs of all processes which belong to
827 A read-write new-line separated values file which exists on
830 When read, it lists the TIDs of all threads which belong to
852 A read-only space separated values file which exists on all
859 A read-write space separated values file which exists on all
863 which are enabled to control resource distribution from the
874 A read-only flat-keyed file which exists on non-root cgroups.
908 in dying state for some time undefined time (which can depend
915 limits, which were active at the moment of cgroup deletion.
918 A read-write single value file which exists on non-root cgroups.
955 base and it does not account for the frequency at which tasks are executed.
957 cpufreq governor about the minimum desired frequency which should always be
958 provided by a CPU, as well as the maximum desired frequency, which should not
975 A read-only flat-keyed file which exists on non-root cgroups.
991 A read-write single value file which exists on non-root
997 A read-write single value file which exists on non-root
1009 A read-write two value file which exists on non-root cgroups.
1016 which indicates that the group may consume upto $MAX in each
1021 A read-only nested-key file which exists on non-root cgroups.
1027 A read-write single value file which exists on non-root cgroups.
1042 A read-write single value file which exists on non-root cgroups.
1080 All memory amounts are in bytes. If a value which is not aligned to
1085 A read-only single value file which exists on non-root
1092 A read-write single value file which exists on non-root
1118 A read-write single value file which exists on non-root
1140 A read-write single value file which exists on non-root
1152 A read-write single value file which exists on non-root
1166 A read-write single value file which exists on non-root
1184 A read-only flat-keyed file which exists on non-root cgroups.
1239 A read-only flat-keyed file which exists on non-root cgroups.
1349 Number of transparent hugepages which were allocated to satisfy
1355 Number of transparent hugepages which were allocated to allow
1360 A read-only single value file which exists on non-root
1367 A read-write single value file which exists on non-root
1374 A read-only flat-keyed file which exists on non-root cgroups.
1395 A read-only nested-key file which exists on non-root cgroups.
1416 more memory. For example, a workload which writes data received from
1428 A memory area is charged to the cgroup which instantiated it and stays
1434 To which cgroup the area will be charged is in-deterministic; however,
1435 over time, the memory area is likely to end up in a cgroup which has
1438 If a cgroup sweeps a considerable amount of memory which is expected
1458 A read-only nested-keyed file which exists on non-root
1483 model based controller (CONFIG_BLK_CGROUP_IOCOST) which
1523 devices which show wide temporary behavior changes - e.g. a
1524 ssd which accepts writes at the line speed for a while and
1538 controller (CONFIG_BLK_CGROUP_IOCOST) which currently
1576 A read-write flat-keyed file which exists on non-root cgroups.
1596 A read-write nested-keyed file which exists on non-root
1635 A read-only nested-key file which exists on non-root cgroups.
1653 maintained for and the io controller defines the io domain which
1664 which affects how cgroup ownership is tracked. Memory is tracked per
1670 which are associated with different cgroups than the one the inode is
1687 The sysctl knobs which affect writeback behavior are applied to cgroup
1787 The number of tasks in a cgroup can be exhausted in ways which other
1800 A read-write single value file which exists on non-root
1806 A read-only single value file which exists on all cgroups.
1839 A read-write multiple values file which exists on non-root
1861 A read-only multiple values file which exists on all
1878 A read-write multiple values file which exists on non-root
1901 A read-only multiple values file which exists on all
1917 A read-write single value file which exists on non-root
2005 structure, which describes the device access attempt: access type
2149 The 'cgroupns root' for a cgroup namespace is the cgroup in which the
2272 selective disabling of cgroup writeback support which is helpful when
2311 type controllers such as freezer which can be useful in all
2319 In practice, these issues heavily limited which controllers could be
2332 There was no limit on how many hierarchies there might be, which meant
2335 in length, which made it highly awkward to manipulate and led to
2336 addition of controllers which existed only to identify membership,
2337 which in turn exacerbated the original problem of proliferating number
2346 In most use cases, putting controllers on hierarchies which are
2368 the application which owns the target process.
2370 cgroup v1 had an ambiguously defined delegation model which got abused
2386 cgroup controllers implemented a number of knobs which would never be
2389 knobs which were not properly abstracted or refined and directly
2403 cgroup v1 allowed threads to be in any cgroups which created an
2415 wasn't obvious or universal, and there were various other knobs which
2422 always added an extra layer of nesting which wouldn't be necessary
2429 knobs to tailor the behavior to specific workloads which would have
2437 This clearly is a problem which needs to be addressed from cgroup core
2492 effective low, which makes delegation of subtrees possible. It also