Lines Matching refs:subsystem
53 A *subsystem* is a module that makes use of the task grouping
55 particular ways. A subsystem is typically a "resource controller" that
58 virtualization subsystem.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
107 At one extreme, each resource controller or subsystem could be in a
179 cgroup_subsys_state objects, one for each cgroup subsystem
184 subsystem state is something that's expected to happen frequently
217 It's not currently possible to bind a new subsystem to an active
218 cgroup hierarchy, or to unbind a subsystem from an active cgroup
231 for each active hierarchy, the subsystem names and the cgroup name
313 the "cpuset" cgroup subsystem, the steps are something like::
435 has processes attached, or is held alive by other subsystem-specific
485 you give a subsystem a name.
487 The name of the subsystem appears as part of the hierarchy description
497 Each kernel subsystem that wants to hook into the generic cgroup
500 with a subsystem ID which will be assigned by the cgroup system.
504 - subsys_id: a unique array index for the subsystem, indicating which
505 entry in cgroup->subsys[] this subsystem should be managing.
507 - name: should be initialized to a unique subsystem name. Should be
510 - early_init: indicate if the subsystem needs early initialization
514 indexed by subsystem ID; this pointer is entirely managed by the
515 subsystem; the generic cgroup code will never touch this pointer.
539 Each subsystem should:
544 Each subsystem may export the following methods. The only mandatory
551 Called to allocate a subsystem state object for a cgroup. The
552 subsystem should allocate its subsystem state object for the passed
554 ERR_PTR() value. On success, the subsystem pointer should point to
556 larger subsystem-specific object), which will be initialized by the
558 create the root subsystem state for this subsystem; this case can be
568 subsystem may choose to fail creation by returning -errno. This
578 @cgrp. @cgrp is being removed and the subsystem should start dropping
581 callback, @cgrp should be considered dead to the subsystem.
586 The cgroup system is about to free @cgrp; the subsystem should free
587 its subsystem state object. By the time this method is called, @cgrp
590 subsystem's create() method has been called for the new cgroup).
596 subsystem returns an error, this will abort the attach operation.
618 when a subsystem is disabled on a cgroup through
622 that the hidden subsystem can return to the initial neutral state.
631 A subsystem whose can_attach() has some side-effects should provide this
632 function, so that the subsystem can implement a rollback. If not, not necessary.
658 Called when a cgroup subsystem is rebound to a different hierarchy