Lines Matching refs:subsystem

49 A *subsystem* is a module that makes use of the task grouping
51 particular ways. A subsystem is typically a "resource controller" that
54 virtualization subsystem.
58 hierarchy, and a set of subsystems; each subsystem has system-specific
103 At one extreme, each resource controller or subsystem could be in a
175    cgroup_subsys_state objects, one for each cgroup subsystem
180    subsystem state is something that's expected to happen frequently
213 It's not currently possible to bind a new subsystem to an active
214 cgroup hierarchy, or to unbind a subsystem from an active cgroup
227 for each active hierarchy, the subsystem names and the cgroup name
309 the "cpuset" cgroup subsystem, the steps are something like:
421 has processes attached, or is held alive by other subsystem-specific
469 you give a subsystem a name.
471 The name of the subsystem appears as part of the hierarchy description
481 Each kernel subsystem that wants to hook into the generic cgroup
484 with a subsystem ID which will be assigned by the cgroup system.
488 - subsys_id: a unique array index for the subsystem, indicating which
489   entry in cgroup->subsys[] this subsystem should be managing.
491 - name: should be initialized to a unique subsystem name. Should be
494 - early_init: indicate if the subsystem needs early initialization
498 indexed by subsystem ID; this pointer is entirely managed by the
499 subsystem; the generic cgroup code will never touch this pointer.
523 Each subsystem should:
528 If a subsystem can be compiled as a module, it should also have in its
533 Each subsystem may export the following methods. The only mandatory
540 Called to allocate a subsystem state object for a cgroup. The
541 subsystem should allocate its subsystem state object for the passed
543 ERR_PTR() value. On success, the subsystem pointer should point to
545 larger subsystem-specific object), which will be initialized by the
547 create the root subsystem state for this subsystem; this case can be
557 subsystem may choose to fail creation by returning -errno. This
567 @cgrp. @cgrp is being removed and the subsystem should start dropping
570 callback, @cgrp should be considered dead to the subsystem.
575 The cgroup system is about to free @cgrp; the subsystem should free
576 its subsystem state object. By the time this method is called, @cgrp
579 subsystem's create() method has been called for the new cgroup).
585 subsystem returns an error, this will abort the attach operation.
607 when a subsystem is disabled on a cgroup through
611 that the hidden subsystem can return to the initial neutral state.
620 A subsystem whose can_attach() has some side-effects should provide this
621 function, so that the subsystem can implement a rollback. If not, not necessary.
643 Called when a cgroup subsystem is rebound to a different hierarchy