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
467 the target resource across its immediate children will be controlled.
475 of CPU cycles and memory to its children, in this case, B. As B has
526 cgroup must create children and transfer all its processes to the
527 children before enabling controllers in its "cgroup.subtree_control"
538 user by granting write access of the directory and its "cgroup.procs",
574 to migrate a target process into a cgroup by writing its PID to the
599 not have write access to its "cgroup.procs" files and thus the write
631 Interface files for a cgroup and its children cgroups occupy the same
659 active children and giving each the fraction matching the ratio of its
701 as long as the usages of all its ancestors are under their
794 - If a controller implements weight based resource distribution, its
943 cgroup to its children.
959 1 if the cgroup or its descendants contains any live
1016 A cgroup can be frozen either by its own settings, or by settings
1107 The interaction of a process with the cpu controller depends on its scheduling
1242 very low priority relative to its peers.
1281 and its descendants.
1288 is within its effective min boundary, the cgroup's memory
1300 the part of parent's protection proportional to its
1307 its memory.min is ignored.
1314 cgroup is within its effective low boundary, the cgroup's
1326 the part of parent's protection proportional to its
1350 job will trigger the reclaim and/or get throttled on its
1356 busy-hitting its memory to slow down reclaim.
1379 The job will trigger the reclaim and/or oom-kill on its next
1385 busy-hitting its memory to slow down reclaim.
1425 The max memory usage recorded for the cgroup and its descendants since
1438 all tasks belonging to the cgroup or to its descendants
1463 high memory pressure even though its usage is under
1791 and its descendants.
1798 this limit, all its further allocations will be throttled to
1812 The max swap usage recorded for the cgroup and its descendants since
2072 the cgroup can use in relation to its siblings.
2221 target the controller doesn't do anything. Once a group starts missing its
2239 Once the victimized group starts meeting its latency target again it will start
2339 controllers cannot prevent, thus warranting its own controller. For
2359 The number of processes currently in the cgroup and its
2365 The maximum value that the number of processes in the cgroup and its
2403 cannot use CPUs or memory nodes not allowed in its parent.
2415 subjected to constraints imposed by its parent and can differ
2436 cgroup by its parent. These CPUs are allowed to be used by
2446 Its value will be affected by CPU hotplug events.
2454 is subjected to constraints imposed by its parent and can differ
2487 this cgroup by its parent. These memory nodes are allowed to
2496 Its value will be affected by memory nodes hotplug events.
2503 to create a new cpuset partition. Its value is not used
2518 of its sibling. If "cpuset.cpus.exclusive" of a sibling cgroup
2519 isn't set, its "cpuset.cpus" value, if set, cannot be a subset
2523 For a parent cgroup, any one of its exclusive CPUs can only
2524 be distributed to at most one of its child cgroups. Having an
2525 exclusive CPU appearing in two or more of its child cgroups is
2529 The root cgroup is a partition root and all its available CPUs
2530 are in its exclusive CPU set.
2538 of this file will always be a subset of its parent's
2539 "cpuset.cpus.exclusive.effective" if its parent is not the root
2566 a partition root at the top of the hierarchy and its descendants
2576 is optional for the creation of a local partition as its
2587 The root cgroup is always a partition root and its state cannot
2592 determined by the value of its "cpuset.cpus.exclusive.effective".
2639 A valid non-root parent partition may distribute out all its CPUs
2640 to its child local partitions when there is no task associated
2644 as all its child local partitions, if present, will become
2703 Each line contains space separated resource name and its configured
2731 device memory regions. Because each memory region may have its own page size,
2813 in the kernel/cgroup/misc.c file. Provider of the resource must set its
2836 the current usage of the resources in the cgroup and its children.::
2844 historical maximum usage of the resources in the cgroup and its
2853 maximum usage of the resources in the cgroup and its children.::
2917 root cgroup. This child cgroup weight is dependent on its thread nice
2944 its "/proc/$PID/cgroup" output restricted to cgroupns root. The
2974 When some thread from a multi-threaded process unshares its cgroup
3005 Each process gets its namespace-specific view of "/proc/$PID/cgroup"
3024 different cgroup), the cgroup path relative to its own cgroup
3032 its relative to the cgroup namespace root of the caller.
3051 namespace should only be exposed to its own cgroupns hierarchy.
3055 (a) the process has CAP_SYS_ADMIN against its current user namespace
3073 filesystem root. The process needs CAP_SYS_ADMIN against its user and
3115 wbc_init_bio() binds the specified bio to its cgroup. Depending on
3160 each controller on its own hierarchy. Only closely related ones, such
3217 exposed this way. For a process to access its own knobs, it has to
3223 that the process would actually be operating on its own sub-hierarchy.
3243 interesting problem where threads belonging to a parent cgroup and its
3258 cgroup to host the threads. The hidden leaf had its own copies of all
3319 implementation, despite its enormous size, does not even provide the
3330 reserve. A cgroup enjoys reclaim protection when it's within its
3332 enjoys having reclaim pressure proportional to its overage when
3333 above its effective low.
3376 groups can sabotage swapping by other means - such as referencing its