Lines Matching full:each

62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy.  Each hierarchy has
67 cgroups. Each hierarchy is a partition of all tasks in the system.
81 tasks in each cgroup.
101 different subsystems - having parallel hierarchies allows each
107 At one extreme, each resource controller or subsystem could be in a
175  - Each task in the system has a reference-counted pointer to a
179    cgroup_subsys_state objects, one for each cgroup subsystem
181    the cgroup of which it's a member in each hierarchy, but this
188    field of each task_struct using the css_set, anchored at
230 Each task under /proc has an added file named 'cgroup' displaying,
231 for each active hierarchy, the subsystem names and the cgroup name
234 Each cgroup is represented by a directory in the cgroup file system
249 Other subsystems such as cpusets may add additional files in each
260 The attachment of each task, automatically inherited at fork by any
274 each cg_cgroup_link is linked into a list of cg_cgroup_links for
279 each css_set that references the cgroup, and sub-iterating over
280 each css_set's task set.
361 for each new cgroup created before that group can be used.
364 different hierarchies of cgroups for each single resource or group of
366 /sys/fs/cgroup and create directories for each cgroup resource or resource
463 Note: Since every task is always a member of exactly one cgroup in each
477 rather than by its set of active subsystems.  Each hierarchy is either
497 Each kernel subsystem that wants to hook into the generic cgroup
513 Each cgroup object created by the system has an array of pointers,
539 Each subsystem should:
544 Each subsystem may export the following methods. The only mandatory
606 Each @tset entry also contains the task's old cgroup and tasks which