admin-guide/cgroup-v1/cgroups.rst

61 every task in the system is in exactly one of the cgroups in the
62 hierarchy, and a set of subsystems; each subsystem has system-specific
67 cgroups. Each hierarchy is a partition of all tasks in the system.
70 instance of the cgroup virtual file system, specify and query to
73 associated with that instance of the cgroup file system.
97 minimal impact on the system fast paths, and provides hooks for
115 university server with various users - students, professors, system
125                In addition (system tasks) are attached to topcpuset (so
126                that they can run anywhere) with a limit of 20%
128        Memory : Professors (50%), Students (30%), system (20%)
130        Disk : Professors (50%), Students (30%), system (20%)
132        Network : WWW browsing (20%), Network File System (60%), others (20%)
177  - Each task in the system has a reference-counted pointer to a
182    registered in the system. There is no direct link from a task to
202    css_set at system boot.
206 In addition, a new file system of type "cgroup" may be mounted, to
229 No new system calls are added for cgroups - all support for
230 querying and modifying cgroups is via this cgroup file system.
234 as the path relative to the root of the cgroup file system.
236 Each cgroup is represented by a directory in the cgroup file system
254 New cgroups are created using the mkdir system call or shell
260 a large system into nested, dynamically changeable, "soft-partitions".
264 on a system into related sets of tasks.  A task may be re-attached to
266 cgroup file system directories.
284 The use of a Linux virtual file system (vfs) to represent the
297 file system) of the abandoned cgroup.  This enables automatic
299 notify_on_release in the root cgroup at system boot is disabled
321     the /sys/fs/cgroup/cpuset virtual file system.
399 tree of the cgroups in the system. For instance, /sys/fs/cgroup/rg1
400 is the cgroup that holds the whole system.
500 system needs to create a cgroup_subsys object. This contains
501 various methods, which are callbacks from the cgroup system, along
502 with a subsystem ID which will be assigned by the cgroup system.
513   at system boot.
515 Each cgroup object created by the system has an array of pointers,
523 system. This should be taken by anything that wants to modify a
559 cgroup system. Note that this will be called at initialization to
588 The cgroup system is about to free @cgrp; the subsystem should free
692      errors. If you use it in the cgroup file system, you won't be