LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, Paul Jackson <pj@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 6/6] mempolicy: update NUMA memory policy documentation
Date: Fri, 29 Feb 2008 17:14:19 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0802291713280.4164@chino.kir.corp.google.com> (raw)
In-Reply-To: <47C8A982.4080302@oracle.com>

On Fri, 29 Feb 2008, Randy Dunlap wrote:

> David Rientjes wrote:
> > Updates Documentation/vm/numa_memory_policy.txt and
> > Documentation/filesystems/tmpfs.txt to describe optional mempolicy mode
> > flags.
> > 
> > Cc: Christoph Lameter <clameter@sgi.com>
> > Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
> > Cc: Andi Kleen <ak@suse.de>
> > Cc: Randy Dunlap <randy.dunlap@oracle.com>
> > Signed-off-by: David Rientjes <rientjes@google.com>
> > Signed-off-by: Paul Jackson <pj@sgi.com>
> > ---
> >  Documentation/filesystems/tmpfs.txt     |   12 +++
> >  Documentation/vm/numa_memory_policy.txt |  131
> > +++++++++++++++++++++++-------
> >  2 files changed, 112 insertions(+), 31 deletions(-)
> > 
> > diff --git a/Documentation/vm/numa_memory_policy.txt
> > b/Documentation/vm/numa_memory_policy.txt
> > --- a/Documentation/vm/numa_memory_policy.txt
> > +++ b/Documentation/vm/numa_memory_policy.txt
> 
> > @@ -231,6 +234,80 @@ Components of Memory Policies
> >  	    the temporary interleaved system default policy works in this
> >  	    mode.
> >  +   Linux memory policy supports the following optional mode flag:
> 
>                                                               flags:
> 
> > +
> > +	MPOL_F_STATIC_NODES:  This flag specifies that the nodemask passed by
> > +	the user should not be remapped if the task or VMA's set of allowed
> > +	nodes changes after the memory policy has been defined.
> > +
> > +	    Without this flag, anytime a mempolicy is rebound because of a
> > +	    change in the set of allowed nodes, the node (Preferred) or
> > +	    nodemask (Bind, Interleave) is remapped to the new set of
> > +	    allowed nodes.  This may result in nodes being used that were
> > +	    previously undesired.
> > +
> > +	    With this flag, if the user specified nodes overlap with the
> 
>                                   user-specified
> 
> > +	    nodes allowed by the task's cpuset, then the memory policy is
> > +	    applied to their intersection.  If the two sets of nodes do not
> > +	    overlap, the Default policy is used.
> > +
> > +	    For example, consider a task that is attached to a cpuset with
> > +	    mems 1-3 that sets an Interleave policy over the same set.  If
> > +	    the cpuset's mems change to 3-5, the Interleave will now occur
> > +	    over nodes 3, 4, and 5.  With this flag, however, since only node
> > +	    3 is allowed from the user's nodemask, the "interleave" only
> > +	    occurs over that node.  If no nodes from the user's nodemask are
> > +	    now allowed, the Default behavior is used.
> > +
> > +	    MPOL_F_STATIC_NODES cannot be used with MPOL_F_RELATIVE_NODES.
> > +
> 

Andrew, please fold this into 
mempolicy-update-numa-memory-policy-documentation.patch if this patchset is 
added to -mm.

Corrects two errors in Documentation/vm/numa_memory_policy.txt as identified by 
Randy Dunlap <randy.dunlap@oracle.com>.

Cc: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Paul Jackson <pj@sgi.com>
Signed-off-by: David Rientjes <rientjes@google.com>
---
 Documentation/vm/numa_memory_policy.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/vm/numa_memory_policy.txt b/Documentation/vm/numa_memory_policy.txt
--- a/Documentation/vm/numa_memory_policy.txt
+++ b/Documentation/vm/numa_memory_policy.txt
@@ -234,7 +234,7 @@ Components of Memory Policies
 	    the temporary interleaved system default policy works in this
 	    mode.
 
-   Linux memory policy supports the following optional mode flag:
+   Linux memory policy supports the following optional mode flags:
 
 	MPOL_F_STATIC_NODES:  This flag specifies that the nodemask passed by
 	the user should not be remapped if the task or VMA's set of allowed
@@ -246,7 +246,7 @@ Components of Memory Policies
 	    allowed nodes.  This may result in nodes being used that were
 	    previously undesired.
 
-	    With this flag, if the user specified nodes overlap with the
+	    With this flag, if the user-specified nodes overlap with the
 	    nodes allowed by the task's cpuset, then the memory policy is
 	    applied to their intersection.  If the two sets of nodes do not
 	    overlap, the Default policy is used.

  reply	other threads:[~2008-03-01  1:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01  0:44 [patch 1/6] mempolicy: convert MPOL constants to enum David Rientjes
2008-03-01  0:45 ` [patch 2/6] mempolicy: support optional mode flags David Rientjes
2008-03-01  0:45   ` [patch 3/6] mempolicy: add MPOL_F_STATIC_NODES flag David Rientjes
2008-03-01  0:45     ` [patch 4/6] mempolicy: add bitmap_onto() and bitmap_fold() operations David Rientjes
2008-03-01  0:45       ` [patch 5/6] mempolicy: add MPOL_F_RELATIVE_NODES flag David Rientjes
2008-03-01  0:45         ` [patch 6/6] mempolicy: update NUMA memory policy documentation David Rientjes
2008-03-01  0:55           ` Randy Dunlap
2008-03-01  1:14             ` David Rientjes [this message]
2008-03-03  7:17 ` [patch 1/6] mempolicy: convert MPOL constants to enum Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-02-25 15:35 David Rientjes
2008-02-25 15:35 ` [patch 2/6] mempolicy: support optional mode flags David Rientjes
2008-02-25 15:35   ` [patch 3/6] mempolicy: add MPOL_F_STATIC_NODES flag David Rientjes
2008-02-25 15:35     ` [patch 4/6] mempolicy: add bitmap_onto() and bitmap_fold() operations David Rientjes
2008-02-25 15:35       ` [patch 5/6] mempolicy: add MPOL_F_RELATIVE_NODES flag David Rientjes
2008-02-25 15:35         ` [patch 6/6] mempolicy: update NUMA memory policy documentation David Rientjes
2008-02-26 17:34           ` Paul Jackson
2008-02-26 21:23             ` David Rientjes

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=alpine.DEB.1.00.0802291713280.4164@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=randy.dunlap@oracle.com \
    --subject='Re: [patch 6/6] mempolicy: update NUMA memory policy documentation' \
    /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).