From: Randy Dunlap <rdunlap@xenotime.net>
To: Paul Menage <paul@paulmenage.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
container cgroup <containers@lists.linux-foundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] cgroups: update documentation on task moving restriction
Date: Sun, 21 Aug 2011 21:15:25 -0700 [thread overview]
Message-ID: <20110821211525.26e793c9.rdunlap@xenotime.net> (raw)
In-Reply-To: <CALdu-PC5_J2-Ss6se8LnoWDf5Ltt3Y9__RXKyTZUXvgBmv60Tg@mail.gmail.com>
On Thu, 18 Aug 2011 00:44:35 -0700 Paul Menage wrote:
> On Wed, Aug 17, 2011 at 7:51 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> > - ns cgroup has been removed.
> > - it's true moving a task to another cgroup can fail.
> >
> > Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
>
> Acked-by: Paul Menage <paul@paulmenage.org>
Applied, thanks.
> > ---
> > Documentation/cgroups/cgroups.txt | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> > index cd67e90..9c452ef 100644
> > --- a/Documentation/cgroups/cgroups.txt
> > +++ b/Documentation/cgroups/cgroups.txt
> > @@ -454,8 +454,8 @@ mounted hierarchy, to remove a task from its current cgroup you must
> > move it into a new cgroup (possibly the root cgroup) by writing to the
> > new cgroup's tasks file.
> >
> > -Note: If the ns cgroup is active, moving a process to another cgroup can
> > -fail.
> > +Note: Due to some restrictions enforced by some cgroup subsystems, moving
> > +a process to another cgroup can fail.
> >
> > 2.3 Mounting hierarchies by name
> > --------------------------------
> > --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-08-22 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 2:51 Li Zefan
2011-08-18 7:44 ` Paul Menage
2011-08-22 4:15 ` Randy Dunlap [this message]
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=20110821211525.26e793c9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=containers@lists.linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=paul@paulmenage.org \
/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®