Lines Matching refs:system

57 every task in the system is in exactly one of the cgroups in the
58 hierarchy, and a set of subsystems; each subsystem has system-specific
63 cgroups. Each hierarchy is a partition of all tasks in the system.
66 instance of the cgroup virtual file system, specify and query to
69 associated with that instance of the cgroup file system.
91 minimal impact on the system fast paths, and provides hooks for
109 university server with various users - students, professors, system
119                In addition (system tasks) are attached to topcpuset (so
122        Memory : Professors (50%), Students (30%), system (20%)
124        Disk : Professors (50%), Students (30%), system (20%)
171  - Each task in the system has a reference-counted pointer to a
176    registered in the system. There is no direct link from a task to
196    css_set at system boot.
200 In addition, a new file system of type "cgroup" may be mounted, to
223 No new system calls are added for cgroups - all support for
224 querying and modifying cgroups is via this cgroup file system.
228 as the path relative to the root of the cgroup file system.
230 Each cgroup is represented by a directory in the cgroup file system
248 New cgroups are created using the mkdir system call or shell
254 a large system into nested, dynamically changeable, "soft-partitions".
258 on a system into related sets of tasks.  A task may be re-attached to
260 cgroup file system directories.
278 The use of a Linux virtual file system (vfs) to represent the
291 file system) of the abandoned cgroup.  This enables automatic
293 notify_on_release in the root cgroup at system boot is disabled
315     the /sys/fs/cgroup/cpuset virtual file system.
390 tree of the cgroups in the system. For instance, /sys/fs/cgroup/rg1
391 is the cgroup that holds the whole system.
482 system needs to create a cgroup_subsys object. This contains
483 various methods, which are callbacks from the cgroup system, along
484 with a subsystem ID which will be assigned by the cgroup system.
495   at system boot.
497 Each cgroup object created by the system has an array of pointers,
505 system. This should be taken by anything that wants to modify a
546 cgroup system. Note that this will be called at initialization to
575 The cgroup system is about to free @cgrp; the subsystem should free
672    errors. If you use it in the cgroup file system, you won't be