[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080627140528.3490.86690.sendpatchset@polaris-admin.engr.sgi.com>
Date: Fri, 27 Jun 2008 07:05:28 -0700
From: Paul Jackson <pj@....com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Michael Kerrisk" <mtk.manpages@...glemail.com>,
"Paul Menage" <menage@...gle.com>, Paul Jackson <pj@....com>,
linux-kernel@...r.kernel.org, "Mike Travis" <travis@....com>
Subject: [PATCH] cpusets: document proc status cpus and mems allowed lists
From: Paul Jackson <pj@....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@....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@....com> 1.650.933.1373
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists