Lines Matching full:its
157 is no longer referenced in its current hierarchy. Because per-cgroup
269 A process can be migrated into a cgroup by writing its PID to the
320 Marking a cgroup threaded makes it join the resource domain of its
371 A domain cgroup is turned into a threaded domain when one of its child
382 threaded domain, its operations are confined inside each threaded
396 threads in the cgroup and its descendants. All consumptions which
401 between threads in a non-leaf cgroup and its child cgroups. Each
417 live processes in it. Its value is 0 if there is no live process in
418 the cgroup and its descendants; otherwise, 1. poll and [id]notify
458 the target resource across its immediate children will be controlled.
466 of CPU cycles and memory to its children, in this case, B. As B has
517 cgroup must create children and transfer all its processes to the
518 children before enabling controllers in its "cgroup.subtree_control"
529 user by granting write access of the directory and its "cgroup.procs",
565 to migrate a target process into a cgroup by writing its PID to the
590 not have write access to its "cgroup.procs" files and thus the write
622 Interface files for a cgroup and its children cgroups occupy the same
650 active children and giving each the fraction matching the ratio of its
692 as long as the usages of all its ancestors are under their
785 - If a controller implements weight based resource distribution, its
934 cgroup to its children.
950 1 if the cgroup or its descendants contains any live
1007 A cgroup can be frozen either by its own settings, or by settings
1193 very low priority relative to its peers.
1232 and its descendants.
1239 is within its effective min boundary, the cgroup's memory
1251 the part of parent's protection proportional to its
1258 its memory.min is ignored.
1265 cgroup is within its effective low boundary, the cgroup's
1277 the part of parent's protection proportional to its
1349 The max memory usage recorded for the cgroup and its descendants since
1362 all tasks belonging to the cgroup or to its descendants
1387 high memory pressure even though its usage is under
1694 and its descendants.
1701 this limit, all its further allocations will be throttled to
1715 The max swap usage recorded for the cgroup and its descendants since
1975 the cgroup can use in relation to its siblings.
2124 target the controller doesn't do anything. Once a group starts missing its
2142 Once the victimized group starts meeting its latency target again it will start
2242 controllers cannot prevent, thus warranting its own controller. For
2262 The number of processes currently in the cgroup and its
2268 The maximum value that the number of processes in the cgroup and its
2306 cannot use CPUs or memory nodes not allowed in its parent.
2318 subjected to constraints imposed by its parent and can differ
2339 cgroup by its parent. These CPUs are allowed to be used by
2349 Its value will be affected by CPU hotplug events.
2357 is subjected to constraints imposed by its parent and can differ
2390 this cgroup by its parent. These memory nodes are allowed to
2399 Its value will be affected by memory nodes hotplug events.
2406 to create a new cpuset partition. Its value is not used
2421 of its sibling. If "cpuset.cpus.exclusive" of a sibling cgroup
2422 isn't set, its "cpuset.cpus" value, if set, cannot be a subset
2426 For a parent cgroup, any one of its exclusive CPUs can only
2427 be distributed to at most one of its child cgroups. Having an
2428 exclusive CPU appearing in two or more of its child cgroups is
2432 The root cgroup is a partition root and all its available CPUs
2433 are in its exclusive CPU set.
2441 of this file will always be a subset of its parent's
2442 "cpuset.cpus.exclusive.effective" if its parent is not the root
2469 a partition root at the top of the hierarchy and its descendants
2479 is optional for the creation of a local partition as its
2490 The root cgroup is always a partition root and its state cannot
2495 determined by the value of its "cpuset.cpus.exclusive.effective".
2542 A valid non-root parent partition may distribute out all its CPUs
2543 to its child local partitions when there is no task associated
2547 as all its child local partitions, if present, will become
2606 Each line contains space separated resource name and its configured
2634 device memory regions. Because each memory region may have its own page size,
2716 in the kernel/cgroup/misc.c file. Provider of the resource must set its
2739 the current usage of the resources in the cgroup and its children.::
2747 historical maximum usage of the resources in the cgroup and its
2756 maximum usage of the resources in the cgroup and its children.::
2820 root cgroup. This child cgroup weight is dependent on its thread nice
2847 its "/proc/$PID/cgroup" output restricted to cgroupns root. The
2877 When some thread from a multi-threaded process unshares its cgroup
2908 Each process gets its namespace-specific view of "/proc/$PID/cgroup"
2927 different cgroup), the cgroup path relative to its own cgroup
2935 its relative to the cgroup namespace root of the caller.
2954 namespace should only be exposed to its own cgroupns hierarchy.
2958 (a) the process has CAP_SYS_ADMIN against its current user namespace
2976 filesystem root. The process needs CAP_SYS_ADMIN against its user and
3018 wbc_init_bio() binds the specified bio to its cgroup. Depending on
3063 each controller on its own hierarchy. Only closely related ones, such
3120 exposed this way. For a process to access its own knobs, it has to
3126 that the process would actually be operating on its own sub-hierarchy.
3146 interesting problem where threads belonging to a parent cgroup and its
3161 cgroup to host the threads. The hidden leaf had its own copies of all
3222 implementation, despite its enormous size, does not even provide the
3233 reserve. A cgroup enjoys reclaim protection when it's within its
3235 enjoys having reclaim pressure proportional to its overage when
3236 above its effective low.
3279 groups can sabotage swapping by other means - such as referencing its