LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* cpuset trivial documentation fix s/N_MEMORY/N_HIGH_MEMORY/
@ 2008-02-19 10:42 KOSAKI Motohiro
  2008-02-19 13:34 ` Paul Jackson
  0 siblings, 1 reply; 6+ messages in thread
From: KOSAKI Motohiro @ 2008-02-19 10:42 UTC (permalink / raw)
  To: kernel list, Trivial patch monkey, Paul Jackson,
	Christoph Lameter, Paul Menage
  Cc: kosaki.motohiro

Hi,

this is easy documentation fix.

current implementation of cpuset track N_HIGH_MEMORY instead N_MEMORY.
(N_MEMORY doesn't exist in current implementation)


Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
CC: Paul Jackson <pj@sgi.com>
CC: Christoph Lameter <clameter@sgi.com>
CC: Paul Menage <menage@google.com>

---
 Documentation/cpusets.txt |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: b/Documentation/cpusets.txt
===================================================================
--- a/Documentation/cpusets.txt 2008-02-14 13:42:22.000000000 +0900
+++ b/Documentation/cpusets.txt 2008-02-19 19:37:14.000000000 +0900
@@ -209,7 +209,7 @@ and name space for cpusets, with a minim
 The cpus and mems files in the root (top_cpuset) cpuset are
 read-only.  The cpus file automatically tracks the value of
 cpu_online_map using a CPU hotplug notifier, and the mems file
-automatically tracks the value of node_states[N_MEMORY]--i.e.,
+automatically tracks the value of node_states[N_HIGH_MEMORY]--i.e.,
 nodes with memory--using the cpuset_track_online_nodes() hook.




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2008-02-29  1:53 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-19 10:42 cpuset trivial documentation fix s/N_MEMORY/N_HIGH_MEMORY/ KOSAKI Motohiro
2008-02-19 13:34 ` Paul Jackson
2008-02-28 22:43   ` Jesper Juhl
2008-02-29  1:43     ` KOSAKI Motohiro
2008-02-29  1:46       ` Jesper Juhl
2008-02-29  1:53         ` KOSAKI Motohiro

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).