From: Paul Jackson <pj@sgi.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: dhaval@linux.vnet.ibm.com, menage@google.com,
akpm@linux-foundation.org, balbir@in.ibm.com,
skumar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
containers@lists.osdl.org
Subject: Re: Attaching PID 0 to a cgroup
Date: Tue, 1 Jul 2008 13:54:09 -0500 [thread overview]
Message-ID: <20080701135409.5e68ccd8.pj@sgi.com> (raw)
In-Reply-To: <486A06B7.7020906@cn.fujitsu.com>
> But it's better to document this.
Good idea.
Acked-by: Paul Jackson <pj@sgi.com>
You (Li Zefan) might want to resend this as a patch, in case Andrew
doesn't happen to see this embedded here.
Something like the following:
Subject: [PATCH] cgroup: document zero pid means current task
From: Li Zefan <lizf@cn.fujitsu.com>
Document that a pid of zero(0) can be used to refer to the
current task when attaching a task to a cgroup, as in the
following usage:
# echo 0 > /dev/cgroup/tasks
This is consistent with existing cpuset behavior.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Acked-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Acked-by: Paul Jackson <pj@sgi.com>
---
cgroups.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/cgroups.txt b/Documentation/cgroups.txt
index 824fc02..213f533 100644
--- a/Documentation/cgroups.txt
+++ b/Documentation/cgroups.txt
@@ -390,6 +390,10 @@ If you have several tasks to attach, you have to do it one after another:
...
# /bin/echo PIDn > tasks
+You can attach the current task by echoing 0:
+
+# /bin/echo 0 > tasks
+
3. Kernel API
=============
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-07-01 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 9:45 Attaching PID 0 to a cgroup Dhaval Giani
2008-07-01 9:47 ` Dhaval Giani
2008-07-01 10:28 ` Li Zefan
2008-07-01 10:51 ` Dhaval Giani
2008-07-01 18:54 ` Paul Jackson [this message]
2008-07-01 19:01 ` Paul Menage
2008-07-01 21:48 ` Andrea Righi
2008-07-01 21:54 ` Dhaval Giani
[not found] ` <20080701215448.GD5893-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-07-03 21:59 ` Matt Helsley
2008-07-03 21:59 ` Matt Helsley
2008-07-03 22:03 ` Paul Menage
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=20080701135409.5e68ccd8.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=skumar@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.