Lines Matching refs:cgroups

5 Documentation/cgroups/cpusets.txt
17   1.1 What are cgroups ?
18   1.2 Why are cgroups needed ?
19   1.3 How are cgroups implemented ?
22   1.6 How do I use cgroups ?
37 1.1 What are cgroups ?
50 facilities provided by cgroups to treat groups of tasks in
56 A *hierarchy* is a set of cgroups arranged in a tree, such that
57 every task in the system is in exactly one of the cgroups in the
63 cgroups. Each hierarchy is a partition of all tasks in the system.
65 User-level code may create and destroy cgroups by name in an
71 On their own, the only use for cgroups is for simple job
73 cgroup support to provide new attributes for cgroups, such as
75 access. For example, cpusets (see Documentation/cgroups/cpusets.txt) allow
79 1.2 Why are cgroups needed ?
96 the division of tasks into cgroups is distinctly different for
101 cgroups.
146 proliferation of such cgroups.
161 multiple separate ones and then associate the new cgroups with the
166 1.3 How are cgroups implemented ?
183    cgroups) are less common. A linked list runs through the cg_list
192 The implementation of cgroups requires a few, simple hooks
195  - in init/main.c, to initialize the root cgroups and initial
201 enable browsing and modifying the cgroups presently known to the
219 child cgroups created below the top-level cgroup, that hierarchy
221 child cgroups then the hierarchy will be deactivated.
223 No new system calls are added for cgroups - all support for
224 querying and modifying cgroups is via this cgroup file system.
248 New cgroups are created using the mkdir system call or shell
250 modified by writing to the appropriate file in that cgroups
253 The named hierarchical structure of nested cgroups allows partitioning
264 desired collection of cgroups then that group is reused, otherwise a new
280 for cgroups, with a minimum of additional kernel code.
292 removal of abandoned cgroups.  The default value of
294 (0).  The default value of other cgroups at creation is the current
305 1.6 How do I use cgroups ?
345 Creating, modifying, using cgroups can be done through the cgroup
358 As explained in section `1.2 Why are cgroups needed?' you should create
359 different hierarchies of cgroups for each single resource or group of
371 While remounting cgroups is currently supported, it is not recommend
390 tree of the cgroups in the system. For instance, /sys/fs/cgroup/rg1
413 You can also create cgroups inside your cgroup by using mkdir in this
420 This will fail if the cgroup is in use (has cgroups inside, or
458 Passing the name=<x> option when mounting a cgroups hierarchy
472 in /proc/mounts and /proc/<pid>/cgroups.
506 cgroup. It may also be taken to prevent cgroups from being
592     they're switching cgroups
649 the default hierarchy (which never has sub-cgroups) and a hierarchy
650 that is being created/destroyed (and hence has no sub-cgroups).