mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Michael Kerrisk" <mtk.manpages@googlemail.com>,
	"Paul Menage" <menage@google.com>, Paul Jackson <pj@sgi.com>,
	linux-kernel@vger.kernel.org, "Mike Travis" <travis@sgi.com>
Subject: [PATCH] cpusets: document proc status cpus and mems allowed lists
Date: Fri, 27 Jun 2008 07:05:28 -0700	[thread overview]
Message-ID: <20080627140528.3490.86690.sendpatchset@polaris-admin.engr.sgi.com> (raw)

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>

---
 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

             reply	other threads:[~2008-06-27 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 14:05 Paul Jackson [this message]
2008-06-27 14:40 ` Michael Kerrisk

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=20080627140528.3490.86690.sendpatchset@polaris-admin.engr.sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=mtk.manpages@googlemail.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®