Lines Matching refs:processes
116 cgroup is a mechanism to organize processes hierarchically and
122 processes. A cgroup controller is usually responsible for
129 same cgroup. On creation, all processes are put in the cgroup that
132 existing descendant processes.
137 processes which belong to the cgroups consisting the inclusive
263 Initially, only the root cgroup exists to which all processes belong.
270 "cgroup.procs". When read, it lists the PIDs of all processes which
288 A cgroup which doesn't have any children or live processes can be
290 have any children and is associated only with zombie processes is
317 the threads of a group of processes. By default, all threads of a
340 resource consumptions whether there are processes in it or not and
379 "cgroup.subtree_control" file while there are processes in the cgroup.
393 all the processes are considered to be in the threaded domain cgroup.
395 processes in the subtree and is not readable in the subtree proper.
423 live processes in it. Its value is 0 if there is no live process in
426 example, to start a clean-up operation after all processes of a given
429 where the numbers in the parentheses represent the numbers of processes
511 only when they don't have any processes of their own. In other words,
512 only domain cgroups which don't contain any processes can have domain
516 of the hierarchy which has it enabled, processes are always only on
518 against internal processes of the parent.
521 processes and anonymous resource consumption which can't be associated
532 cgroup must create children and transfer all its processes to the
561 organize processes inside it as it sees fit and further distribute the
575 A delegated sub-hierarchy is contained in the sense that processes
589 processes around freely in the delegated sub-hierarchy it can't pull
594 all processes under C0 and C1 belong to U0::
626 As such, migrating processes across cgroups frequently as a means to
737 resource is mandatory for execution of processes, process migrations
886 When read, it lists the PIDs of all processes which belong to
905 as all the processes belong to the thread root. Writing is
963 processes; otherwise, 0.
1030 descendant cgroups. This means that all belonging processes will
1056 be killed. This means that all processes located in the affected cgroup
1110 realtime processes. For a kernel built with the CONFIG_RT_GROUP_SCHED option
1111 enabled for group scheduling of realtime processes, the cpu controller can only
1112 be enabled when all RT processes are in the root cgroup. Be aware that system
1113 management software may already have placed RT processes into non-root cgroups
1114 during the system boot process, and these processes may need to be moved to the
1119 the interface files either affect realtime processes or account for them. See
1122 realtime processes irrespective of CONFIG_RT_GROUP_SCHED.
1130 processes can be categorized as follows:
1134 * Everything else: ``SCHED_{FIFO,RR,DEADLINE}`` and processes under a BPF scheduler
1148 processes in the cgroup:
1155 only the processes under the fair-class scheduler:
1173 This file affects only processes under the fair-class scheduler and a BPF
1189 This file affects only processes under the fair-class scheduler and a BPF
1205 This file affects only processes under the fair-class scheduler.
1213 This file affects only processes under the fair-class scheduler.
1221 This file accounts for all the processes in the cgroup.
1233 including those of realtime processes.
1239 This file affects all the processes in the cgroup.
1251 including those of realtime processes.
1253 This file affects all the processes in the cgroup.
1265 This file affects only processes under the fair-class scheduler.
1355 over the high boundary, the processes of the cgroup are
1365 reclaim is bypassed. This is useful for admin processes that
1395 processes that need to dynamically adjust the job's memory limits
1486 The number of times processes of the cgroup are
1507 The number of processes belonging to this cgroup
1966 A memory area may be used by processes belonging to different cgroups.
2397 Hard limit of number of processes.
2402 The number of processes currently in the cgroup and its
2408 The maximum value that the number of processes in the cgroup and its
2417 The number of times the cgroup's total number of processes hit the pids.max
2428 processes to the cgroup such that pids.current is larger than
2984 Root cgroup processes are hosted in an implicit leaf child node.
3006 a set of cgroups and namespaces are intended to isolate processes the
3008 to the isolated processes. For example::
3014 and undesirable to expose to the isolated processes. cgroup namespace
3035 A cgroup namespace is alive as long as there are processes inside or
3261 itself; thus, unlike service-level organization of processes,
3406 aggressively will not terminate the processes, but instead it will