Lines Matching refs:subsystems

47 or more subsystems.
58 hierarchy, and a set of subsystems; each subsystem has system-specific
72 tracking. The intention is that other subsystems hook into the generic
92 specific subsystems such as cpusets to provide additional behaviour as
97 different subsystems - having parallel hierarchies allows each
100 unrelated subsystems needed to be forced into the same tree of
104 separate hierarchy; at the other extreme, all subsystems
137 (by putting those resource subsystems in different hierarchies),
203 comma-separated list of subsystems to mount as the filesystem mount
205 mount a hierarchy containing all registered subsystems.
207 If an active hierarchy with exactly the same set of subsystems already
209 matches, and any of the requested subsystems are in use in an existing
211 is activated, associated with the requested subsystems.
245 Other subsystems such as cpusets may add additional files in each
348 To mount a cgroup hierarchy with all available subsystems, type:
354 Note: Some subsystems do not work without some user input first.  For instance,
368 subsystems, type:
372 to use it. Remounting allows changing bound subsystems and
384 Note that changing the set of subsystems is currently only supported
386 the ability to arbitrarily bind/unbind subsystems from an existing
408 (plus whatever files added by the attached subsystems)
452 Note: Due to some restrictions enforced by some cgroup subsystems, moving
461 rather than by its set of active subsystems.  Each hierarchy is either
467 specify subsystems manually; the legacy behaviour of mounting all
468 subsystems when none are explicitly specified is not supported when
604 subsystems depend on it.  cgroup core makes such a css invisible by
617 This will be called only about subsystems whose can_attach() operation have