From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Paul Menage" <menage@google.com>,
linux-kernel@vger.kernel.org, "Mike Travis" <travis@sgi.com>
Subject: Re: [PATCH] cpusets: document proc status cpus and mems allowed lists
Date: Fri, 27 Jun 2008 16:40:18 +0200 [thread overview]
Message-ID: <cfd18e0f0806270740v23e0e0e4jc7ca520dcf31540f@mail.gmail.com> (raw)
In-Reply-To: <20080627140528.3490.86690.sendpatchset@polaris-admin.engr.sgi.com>
On Fri, Jun 27, 2008 at 4:05 PM, Paul Jackson <pj@sgi.com> wrote:
> From: Paul Jackson <pj@sgi.com>
>
> Provide a little documentation for the two new fields,
> Cpus_allowed_list and Mems_allowed_list, that were
> added to each /proc/<pid>/status file a while back.
>
> Signed-off-by: Paul Jackson <pj@sgi.com>
Acked-by: Michael Kerrisk <mtk,manpages@gmail.com>
> ---
> Documentation/cpusets.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> --- 2.6.26-rc5-mm3.orig/Documentation/cpusets.txt 2008-06-27 06:20:55.000000000 -0700
> +++ 2.6.26-rc5-mm3/Documentation/cpusets.txt 2008-06-27 06:55:34.609862065 -0700
> @@ -154,13 +154,15 @@ browsing and modifying the cpusets prese
> new system calls are added for cpusets - all support for querying and
> modifying cpusets is via this cpuset file system.
>
> -The /proc/<pid>/status file for each task has two added lines,
> +The /proc/<pid>/status file for each task has four added lines,
> displaying the tasks cpus_allowed (on which CPUs it may be scheduled)
> and mems_allowed (on which Memory Nodes it may obtain memory),
> -in the format seen in the following example:
> +in the two formats seen in the following example:
>
> Cpus_allowed: ffffffff,ffffffff,ffffffff,ffffffff
> + Cpus_allowed_list: 0-127
> Mems_allowed: ffffffff,ffffffff
> + Mems_allowed_list: 0-63
>
> Each cpuset is represented by a directory in the cgroup file system
> containing (on top of the standard cgroup files) the following
>
> --
> I won't rest till it's the best ...
> Programmer, Linux Scalability
> Paul Jackson <pj@sgi.com> 1.650.933.1373
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2008-06-27 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 14:05 Paul Jackson
2008-06-27 14:40 ` Michael Kerrisk [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=cfd18e0f0806270740v23e0e0e4jc7ca520dcf31540f@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=travis@sgi.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 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®