Lines Matching full: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
98 specific subsystems such as cpusets to provide additional behaviour as
103 different subsystems - having parallel hierarchies allows each
106 unrelated subsystems needed to be forced into the same tree of
110 separate hierarchy; at the other extreme, all subsystems
143 (by putting those resource subsystems in different hierarchies),
209 comma-separated list of subsystems to mount as the filesystem mount
211 mount a hierarchy containing all registered subsystems.
213 If an active hierarchy with exactly the same set of subsystems already
215 matches, and any of the requested subsystems are in use in an existing
217 is activated, associated with the requested subsystems.
251 Other subsystems such as cpusets may add additional files in each
354 To mount a cgroup hierarchy with all available subsystems, type::
361 Note: Some subsystems do not work without some user input first.  For instance,
375 subsystems, type::
380 to use it. Remounting allows changing bound subsystems and
393 Note that changing the set of subsystems is currently only supported
395 the ability to arbitrarily bind/unbind subsystems from an existing
421   (plus whatever files added by the attached subsystems)
470 Note: Due to some restrictions enforced by some cgroup subsystems, moving
479 rather than by its set of active subsystems.  Each hierarchy is either
485 specify subsystems manually; the legacy behaviour of mounting all
486 subsystems when none are explicitly specified is not supported when
530 Subsystems can take/release the cgroup_mutex via the functions
622 subsystems depend on it.  cgroup core makes such a css invisible by
635 This will be called only about subsystems whose can_attach() operation have