Lines Matching full:its
156 is no longer referenced in its current hierarchy. Because per-cgroup
268 A process can be migrated into a cgroup by writing its PID to the
319 Marking a cgroup threaded makes it join the resource domain of its
370 A domain cgroup is turned into a threaded domain when one of its child
381 threaded domain, its operations are confined inside each threaded
395 threads in the cgroup and its descendants. All consumptions which
400 between threads in a non-leaf cgroup and its child cgroups. Each
416 live processes in it. Its value is 0 if there is no live process in
417 the cgroup and its descendants; otherwise, 1. poll and [id]notify
457 the target resource across its immediate children will be controlled.
465 of CPU cycles and memory to its children, in this case, B. As B has
516 cgroup must create children and transfer all its processes to the
517 children before enabling controllers in its "cgroup.subtree_control"
528 user by granting write access of the directory and its "cgroup.procs",
564 to migrate a target process into a cgroup by writing its PID to the
589 not have write access to its "cgroup.procs" files and thus the write
621 Interface files for a cgroup and its children cgroups occupy the same
649 active children and giving each the fraction matching the ratio of its
691 as long as the usages of all its ancestors are under their
784 - If a controller implements weight based resource distribution, its
933 cgroup to its children.
949 1 if the cgroup or its descendants contains any live
1006 A cgroup can be frozen either by its own settings, or by settings
1192 very low priority relative to its peers.
1231 and its descendants.
1238 is within its effective min boundary, the cgroup's memory
1250 the part of parent's protection proportional to its
1257 its memory.min is ignored.
1264 cgroup is within its effective low boundary, the cgroup's
1276 the part of parent's protection proportional to its
1348 The max memory usage recorded for the cgroup and its descendants since
1361 all tasks belonging to the cgroup or to its descendants
1386 high memory pressure even though its usage is under
1688 and its descendants.
1695 this limit, all its further allocations will be throttled to
1709 The max swap usage recorded for the cgroup and its descendants since
1969 the cgroup can use in relation to its siblings.
2118 target the controller doesn't do anything. Once a group starts missing its
2136 Once the victimized group starts meeting its latency target again it will start
2236 controllers cannot prevent, thus warranting its own controller. For
2256 The number of processes currently in the cgroup and its
2262 The maximum value that the number of processes in the cgroup and its
2300 cannot use CPUs or memory nodes not allowed in its parent.
2312 subjected to constraints imposed by its parent and can differ
2333 cgroup by its parent. These CPUs are allowed to be used by
2343 Its value will be affected by CPU hotplug events.
2351 is subjected to constraints imposed by its parent and can differ
2384 this cgroup by its parent. These memory nodes are allowed to
2393 Its value will be affected by memory nodes hotplug events.
2400 to create a new cpuset partition. Its value is not used
2415 of its sibling. If "cpuset.cpus.exclusive" of a sibling cgroup
2416 isn't set, its "cpuset.cpus" value, if set, cannot be a subset
2420 For a parent cgroup, any one of its exclusive CPUs can only
2421 be distributed to at most one of its child cgroups. Having an
2422 exclusive CPU appearing in two or more of its child cgroups is
2426 The root cgroup is a partition root and all its available CPUs
2427 are in its exclusive CPU set.
2435 of this file will always be a subset of its parent's
2436 "cpuset.cpus.exclusive.effective" if its parent is not the root
2463 a partition root at the top of the hierarchy and its descendants
2473 is optional for the creation of a local partition as its
2484 The root cgroup is always a partition root and its state cannot
2489 determined by the value of its "cpuset.cpus.exclusive.effective".
2536 A valid non-root parent partition may distribute out all its CPUs
2537 to its child local partitions when there is no task associated
2541 as all its child local partitions, if present, will become
2600 Each line contains space separated resource name and its configured
2667 in the kernel/cgroup/misc.c file. Provider of the resource must set its
2690 the current usage of the resources in the cgroup and its children.::
2698 historical maximum usage of the resources in the cgroup and its
2707 maximum usage of the resources in the cgroup and its children.::
2771 root cgroup. This child cgroup weight is dependent on its thread nice
2798 its "/proc/$PID/cgroup" output restricted to cgroupns root. The
2828 When some thread from a multi-threaded process unshares its cgroup
2859 Each process gets its namespace-specific view of "/proc/$PID/cgroup"
2878 different cgroup), the cgroup path relative to its own cgroup
2886 its relative to the cgroup namespace root of the caller.
2905 namespace should only be exposed to its own cgroupns hierarchy.
2909 (a) the process has CAP_SYS_ADMIN against its current user namespace
2927 filesystem root. The process needs CAP_SYS_ADMIN against its user and
2969 wbc_init_bio() binds the specified bio to its cgroup. Depending on
3014 each controller on its own hierarchy. Only closely related ones, such
3071 exposed this way. For a process to access its own knobs, it has to
3077 that the process would actually be operating on its own sub-hierarchy.
3097 interesting problem where threads belonging to a parent cgroup and its
3112 cgroup to host the threads. The hidden leaf had its own copies of all
3173 implementation, despite its enormous size, does not even provide the
3184 reserve. A cgroup enjoys reclaim protection when it's within its
3186 enjoys having reclaim pressure proportional to its overage when
3187 above its effective low.
3230 groups can sabotage swapping by other means - such as referencing its