On Wed, Mar 09, 2011 at 04:09:29PM -0500, Eric B Munson wrote: > The cgroup documentation does not specify how a process can be removed from a > particular group. This patch adds a note at the end of the simple example > about how this is done. Also, some cgroups (like cpusets) require user input > before a new group can be used. This is noted in the patch as well. > > Signed-off-by: Eric B Munson <emunson@xxxxxxxxx> > --- > Documentation/cgroups/cgroups.txt | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt > index 44b8b7a..6c975a1 100644 > --- a/Documentation/cgroups/cgroups.txt > +++ b/Documentation/cgroups/cgroups.txt > @@ -349,6 +349,10 @@ To mount a cgroup hierarchy with all available subsystems, type: > The "xxx" is not interpreted by the cgroup code, but will appear in > /proc/mounts so may be any useful identifying string that you like. > > +Note: Some subsystems do not work without some user input first. For instance, > +if cpusets are enabled the user will have to populate the cpus and mems files > +for each new cgroup created before that group can be used. > + > To mount a cgroup hierarchy with just the cpuset and memory > subsystems, type: > # mount -t cgroup -o cpuset,memory hier1 /dev/cgroup > @@ -426,6 +430,9 @@ You can attach the current shell task by echoing 0: > > # echo 0 > tasks > > +Note: To remove a task from a cgroup you must write its PID to the root > +tasks file. > + 'to tasks file of another cgroup.'? > 2.3 Mounting hierarchies by name > -------------------------------- > > -- > 1.7.1 > > _______________________________________________ > Containers mailing list > Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linux-foundation.org/mailman/listinfo/containers -- Kirill A. Shutemov _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
