Lines Matching full:its
156 is no longer referenced in its current hierarchy. Because per-cgroup
261 A process can be migrated into a cgroup by writing its PID to the
312 Marking a cgroup threaded makes it join the resource domain of its
363 A domain cgroup is turned into a threaded domain when one of its child
374 threaded domain, its operations are confined inside each threaded
388 threads in the cgroup and its descendants. All consumptions which
393 between threads in a non-leaf cgroup and its child cgroups. Each
409 live processes in it. Its value is 0 if there is no live process in
410 the cgroup and its descendants; otherwise, 1. poll and [id]notify
450 the target resource across its immediate children will be controlled.
458 of CPU cycles and memory to its children, in this case, B. As B has
509 cgroup must create children and transfer all its processes to the
510 children before enabling controllers in its "cgroup.subtree_control"
521 user by granting write access of the directory and its "cgroup.procs",
555 to migrate a target process into a cgroup by writing its PID to the
580 not have write access to its "cgroup.procs" files and thus the write
612 Interface files for a cgroup and its children cgroups occupy the same
640 active children and giving each the fraction matching the ratio of its
682 as long as the usages of all its ancestors are under their
775 - If a controller implements weight based resource distribution, its
924 cgroup to its children.
940 1 if the cgroup or its descendants contains any live
989 A cgroup can be frozen either by its own settings, or by settings
1172 very low priority relative to its peers.
1211 and its descendants.
1218 is within its effective min boundary, the cgroup's memory
1230 the part of parent's protection proportional to its
1237 its memory.min is ignored.
1244 cgroup is within its effective low boundary, the cgroup's
1256 the part of parent's protection proportional to its
1325 The max memory usage recorded for the cgroup and its
1334 all tasks belonging to the cgroup or to its descendants
1359 high memory pressure even though its usage is under
1624 and its descendants.
1631 this limit, all its further allocations will be throttled to
1646 The max swap usage recorded for the cgroup and its
1699 created, it inherits the current value of its parent.
1899 the cgroup can use in relation to its siblings.
2048 target the controller doesn't do anything. Once a group starts missing its
2066 Once the victimized group starts meeting its latency target again it will start
2166 controllers cannot prevent, thus warranting its own controller. For
2186 The number of processes currently in the cgroup and its
2210 cannot use CPUs or memory nodes not allowed in its parent.
2222 subjected to constraints imposed by its parent and can differ
2243 cgroup by its parent. These CPUs are allowed to be used by
2253 Its value will be affected by CPU hotplug events.
2261 is subjected to constraints imposed by its parent and can differ
2294 this cgroup by its parent. These memory nodes are allowed to
2303 Its value will be affected by memory nodes hotplug events.
2310 to create a new cpuset partition. Its value is not used
2324 list of CPUs must be exclusive with respect to its sibling.
2326 For a parent cgroup, any one of its exclusive CPUs can only
2327 be distributed to at most one of its child cgroups. Having an
2328 exclusive CPU appearing in two or more of its child cgroups is
2332 The root cgroup is a partition root and all its available CPUs
2333 are in its exclusive CPU set.
2341 file will always be a subset of "cpuset.cpus" and its parent's
2342 "cpuset.cpus.exclusive.effective" if its parent is not the root
2369 a partition root at the top of the hierarchy and its descendants
2379 is optional for the creation of a local partition as its
2390 The root cgroup is always a partition root and its state cannot
2395 determined by the value of its "cpuset.cpus.exclusive.effective".
2442 A valid non-root parent partition may distribute out all its CPUs
2443 to its child local partitions when there is no task associated
2447 as all its child local partitions, if present, will become
2506 Each line contains space separated resource name and its configured
2573 in the kernel/cgroup/misc.c file. Provider of the resource must set its
2596 the current usage of the resources in the cgroup and its children.::
2604 maximum usage of the resources in the cgroup and its children.::
2663 root cgroup. This child cgroup weight is dependent on its thread nice
2690 its "/proc/$PID/cgroup" output restricted to cgroupns root. The
2720 When some thread from a multi-threaded process unshares its cgroup
2751 Each process gets its namespace-specific view of "/proc/$PID/cgroup"
2770 different cgroup), the cgroup path relative to its own cgroup
2778 its relative to the cgroup namespace root of the caller.
2797 namespace should only be exposed to its own cgroupns hierarchy.
2801 (a) the process has CAP_SYS_ADMIN against its current user namespace
2819 filesystem root. The process needs CAP_SYS_ADMIN against its user and
2861 wbc_init_bio() binds the specified bio to its cgroup. Depending on
2906 each controller on its own hierarchy. Only closely related ones, such
2963 exposed this way. For a process to access its own knobs, it has to
2969 that the process would actually be operating on its own sub-hierarchy.
2989 interesting problem where threads belonging to a parent cgroup and its
3004 cgroup to host the threads. The hidden leaf had its own copies of all
3065 implementation, despite its enormous size, does not even provide the
3076 reserve. A cgroup enjoys reclaim protection when it's within its
3078 enjoys having reclaim pressure proportional to its overage when
3079 above its effective low.
3122 groups can sabotage swapping by other means - such as referencing its