Lines Matching refs:subsystems

51 or more subsystems.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
76 tracking. The intention is that other subsystems hook into the generic
96 specific subsystems such as cpusets to provide additional behaviour as
101 different subsystems - having parallel hierarchies allows each
104 unrelated subsystems needed to be forced into the same tree of
108 separate hierarchy; at the other extreme, all subsystems
141 (by putting those resource subsystems in different hierarchies),
207 comma-separated list of subsystems to mount as the filesystem mount
209 mount a hierarchy containing all registered subsystems.
211 If an active hierarchy with exactly the same set of subsystems already
213 matches, and any of the requested subsystems are in use in an existing
215 is activated, associated with the requested subsystems.
249 Other subsystems such as cpusets may add additional files in each
352 To mount a cgroup hierarchy with all available subsystems, type::
359 Note: Some subsystems do not work without some user input first.  For instance,
373 subsystems, type::
378 to use it. Remounting allows changing bound subsystems and
391 Note that changing the set of subsystems is currently only supported
393 the ability to arbitrarily bind/unbind subsystems from an existing
419   (plus whatever files added by the attached subsystems)
468 Note: Due to some restrictions enforced by some cgroup subsystems, moving
477 rather than by its set of active subsystems.  Each hierarchy is either
483 specify subsystems manually; the legacy behaviour of mounting all
484 subsystems when none are explicitly specified is not supported when
620 subsystems depend on it.  cgroup core makes such a css invisible by
633 This will be called only about subsystems whose can_attach() operation have