mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Eric B Munson <emunson@mgebm.net>
Cc: containers@lists.linux-foundation.org, rdunlap@xenotime.net,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: cgroups: Add notes on removing PIDs from tasks and cgroups requiring setup
Date: Thu, 10 Mar 2011 01:07:20 +0200	[thread overview]
Message-ID: <20110309230720.GA32096@shutemov.name> (raw)
In-Reply-To: <1299704969-4485-1-git-send-email-emunson@mgebm.net>

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@mgebm.net>
> ---
>  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@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers

-- 
 Kirill A. Shutemov

  reply	other threads:[~2011-03-09 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:09 Eric B Munson
2011-03-09 23:07 ` Kirill A. Shutemov [this message]
2011-03-09 23:13 ` Paul Menage
2011-03-10 14:44   ` Mike Heffner
2011-03-10 16:59   ` Eric B Munson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110309230720.GA32096@shutemov.name \
    --to=kirill@shutemov.name \
    --cc=containers@lists.linux-foundation.org \
    --cc=emunson@mgebm.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®