LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: kernel list <linux-kernel@vger.kernel.org>,
	Trivial patch monkey <trivial@kernel.org>,
	Paul Jackson <pj@sgi.com>, Christoph Lameter <clameter@sgi.com>,
	Paul Menage <menage@google.com>
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: cpuset trivial documentation fix s/N_MEMORY/N_HIGH_MEMORY/
Date: Tue, 19 Feb 2008 19:42:49 +0900	[thread overview]
Message-ID: <20080219193503.94A0.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)

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.




             reply	other threads:[~2008-02-19 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 10:42 KOSAKI Motohiro [this message]
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

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=20080219193503.94A0.KOSAKI.MOTOHIRO@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=pj@sgi.com \
    --cc=trivial@kernel.org \
    --subject='Re: cpuset trivial documentation fix s/N_MEMORY/N_HIGH_MEMORY/' \
    /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

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