Lines Matching full:its
162 is no longer referenced in its current hierarchy. Because per-cgroup
274 A process can be migrated into a cgroup by writing its PID to the
325 Marking a cgroup threaded makes it join the resource domain of its
376 A domain cgroup is turned into a threaded domain when one of its child
387 threaded domain, its operations are confined inside each threaded
401 threads in the cgroup and its descendants. All consumptions which
406 between threads in a non-leaf cgroup and its child cgroups. Each
422 live processes in it. Its value is 0 if there is no live process in
423 the cgroup and its descendants; otherwise, 1. poll and [id]notify
472 the target resource across its immediate children will be controlled.
480 of CPU cycles and memory to its children, in this case, B. As B has
531 cgroup must create children and transfer all its processes to the
532 children before enabling controllers in its "cgroup.subtree_control"
543 user by granting write access of the directory and its "cgroup.procs",
579 to migrate a target process into a cgroup by writing its PID to the
604 not have write access to its "cgroup.procs" files and thus the write
636 Interface files for a cgroup and its children cgroups occupy the same
664 active children and giving each the fraction matching the ratio of its
706 as long as the usages of all its ancestors are under their
799 - If a controller implements weight based resource distribution, its
948 cgroup to its children.
964 1 if the cgroup or its descendants contains any live
1039 A cgroup can be frozen either by its own settings, or by settings
1130 The interaction of a process with the cpu controller depends on its scheduling
1265 very low priority relative to its peers.
1304 and its descendants.
1311 is within its effective min boundary, the cgroup's memory
1323 the part of parent's protection proportional to its
1330 its memory.min is ignored.
1337 cgroup is within its effective low boundary, the cgroup's
1349 the part of parent's protection proportional to its
1373 job will trigger the reclaim and/or get throttled on its
1379 busy-hitting its memory to slow down reclaim.
1402 The job will trigger the reclaim and/or oom-kill on its next
1408 busy-hitting its memory to slow down reclaim.
1448 The max memory usage recorded for the cgroup and its descendants since
1461 all tasks belonging to the cgroup or to its descendants
1486 high memory pressure even though its usage is under
1814 and its descendants.
1821 this limit, all its further allocations will be throttled to
1835 The max swap usage recorded for the cgroup and its descendants since
2095 the cgroup can use in relation to its siblings.
2244 target the controller doesn't do anything. Once a group starts missing its
2262 Once the victimized group starts meeting its latency target again it will start
2362 controllers cannot prevent, thus warranting its own controller. For
2382 The number of processes currently in the cgroup and its
2388 The maximum value that the number of processes in the cgroup and its
2426 cannot use CPUs or memory nodes not allowed in its parent.
2438 subjected to constraints imposed by its parent and can differ
2459 cgroup by its parent. These CPUs are allowed to be used by
2469 Its value will be affected by CPU hotplug events.
2477 is subjected to constraints imposed by its parent and can differ
2510 this cgroup by its parent. These memory nodes are allowed to
2519 Its value will be affected by memory nodes hotplug events.
2526 to create a new cpuset partition. Its value is not used
2541 of its sibling. If "cpuset.cpus.exclusive" of a sibling cgroup
2542 isn't set, its "cpuset.cpus" value, if set, cannot be a subset
2546 For a parent cgroup, any one of its exclusive CPUs can only
2547 be distributed to at most one of its child cgroups. Having an
2548 exclusive CPU appearing in two or more of its child cgroups is
2552 The root cgroup is a partition root and all its available CPUs
2553 are in its exclusive CPU set.
2561 of this file will always be a subset of its parent's
2562 "cpuset.cpus.exclusive.effective" if its parent is not the root
2589 a partition root at the top of the hierarchy and its descendants
2599 is optional for the creation of a local partition as its
2610 The root cgroup is always a partition root and its state cannot
2615 determined by the value of its "cpuset.cpus.exclusive.effective".
2662 A valid non-root parent partition may distribute out all its CPUs
2663 to its child local partitions when there is no task associated
2667 as all its child local partitions, if present, will become
2726 Each line contains space separated resource name and its configured
2754 device memory regions. Because each memory region may have its own page size,
2836 in the kernel/cgroup/misc.c file. Provider of the resource must set its
2859 the current usage of the resources in the cgroup and its children.::
2867 historical maximum usage of the resources in the cgroup and its
2876 maximum usage of the resources in the cgroup and its children.::
2940 root cgroup. This child cgroup weight is dependent on its thread nice
2967 its "/proc/$PID/cgroup" output restricted to cgroupns root. The
2997 When some thread from a multi-threaded process unshares its cgroup
3028 Each process gets its namespace-specific view of "/proc/$PID/cgroup"
3047 different cgroup), the cgroup path relative to its own cgroup
3055 its relative to the cgroup namespace root of the caller.
3074 namespace should only be exposed to its own cgroupns hierarchy.
3078 (a) the process has CAP_SYS_ADMIN against its current user namespace
3096 filesystem root. The process needs CAP_SYS_ADMIN against its user and
3138 wbc_init_bio() binds the specified bio to its cgroup. Depending on
3183 each controller on its own hierarchy. Only closely related ones, such
3240 exposed this way. For a process to access its own knobs, it has to
3246 that the process would actually be operating on its own sub-hierarchy.
3266 interesting problem where threads belonging to a parent cgroup and its
3281 cgroup to host the threads. The hidden leaf had its own copies of all
3342 implementation, despite its enormous size, does not even provide the
3353 reserve. A cgroup enjoys reclaim protection when it's within its
3355 enjoys having reclaim pressure proportional to its overage when
3356 above its effective low.
3399 groups can sabotage swapping by other means - such as referencing its