Lines Matching refs:cgroups

21 	1.1 What are cgroups ?
22 	1.2 Why are cgroups needed ?
23 	1.3 How are cgroups implemented ?
26 	1.6 How do I use cgroups ?
41 1.1 What are cgroups ?
54 facilities provided by cgroups to treat groups of tasks in
60 A *hierarchy* is a set of cgroups arranged in a tree, such that
61 every task in the system is in exactly one of the cgroups in the
67 cgroups. Each hierarchy is a partition of all tasks in the system.
69 User-level code may create and destroy cgroups by name in an
75 On their own, the only use for cgroups is for simple job
77 cgroup support to provide new attributes for cgroups, such as
83 1.2 Why are cgroups needed ?
100 the division of tasks into cgroups is distinctly different for
105 cgroups.
150 proliferation of such cgroups.
165 multiple separate ones and then associate the new cgroups with the
170 1.3 How are cgroups implemented ?
187    cgroups) are less common. A linked list runs through the cg_list
196 The implementation of cgroups requires a few, simple hooks
199  - in init/main.c, to initialize the root cgroups and initial
205 enable browsing and modifying the cgroups presently known to the
223 child cgroups created below the top-level cgroup, that hierarchy
225 child cgroups then the hierarchy will be deactivated.
227 No new system calls are added for cgroups - all support for
228 querying and modifying cgroups is via this cgroup file system.
252 New cgroups are created using the mkdir system call or shell
254 modified by writing to the appropriate file in that cgroups
257 The named hierarchical structure of nested cgroups allows partitioning
268 desired collection of cgroups then that group is reused, otherwise a new
284 for cgroups, with a minimum of additional kernel code.
296 removal of abandoned cgroups.  The default value of
298 (0).  The default value of other cgroups at creation is the current
309 1.6 How do I use cgroups ?
349 Creating, modifying, using cgroups can be done through the cgroup
363 As explained in section `1.2 Why are cgroups needed?` you should create
364 different hierarchies of cgroups for each single resource or group of
377 While remounting cgroups is currently supported, it is not recommend
397 tree of the cgroups in the system. For instance, /sys/fs/cgroup/rg1
425 You can also create cgroups inside your cgroup by using mkdir in this
434 This will fail if the cgroup is in use (has cgroups inside, or
474 Passing the name=<x> option when mounting a cgroups hierarchy
488 in /proc/mounts and /proc/<pid>/cgroups.
522 cgroup. It may also be taken to prevent cgroups from being
603     they're switching cgroups
660 the default hierarchy (which never has sub-cgroups) and a hierarchy
661 that is being created/destroyed (and hence has no sub-cgroups).