linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-numa@vger.kernel.org, eric.whitney@hp.com
Subject: Re: [PATCH 9/15] Mempolicy: Use MPOL_PREFERRED for system-wide default policy
Date: Mon, 14 Apr 2008 16:05:20 -0400	[thread overview]
Message-ID: <1208203520.5453.8.camel@localhost> (raw)
In-Reply-To: <20080414102321.c737314a.randy.dunlap@oracle.com>

On Mon, 2008-04-14 at 10:23 -0700, Randy Dunlap wrote:
> On Fri, 04 Apr 2008 11:00:40 -0400 Lee Schermerhorn wrote:
> 
> > PATCH 09/15 Mempolicy:  Use MPOL_PREFERRED for system-wide default policy
> > 
> > Against:  2.6.25-rc8-mm1
> > 
> > Signed-off-by:  Lee Schermerhorn <lee.schermerhorn@hp.com>
> > 
> >  Documentation/vm/numa_memory_policy.txt |   52 ++++++++----------------
> >  mm/mempolicy.c                          |   68 +++++++++++++++++++-------------
> >  2 files changed, 59 insertions(+), 61 deletions(-)
> > 
> > Index: linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt
> > ===================================================================
> > --- linux-2.6.25-rc8-mm1.orig/Documentation/vm/numa_memory_policy.txt	2008-04-02 17:47:26.000000000 -0400
> > +++ linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt	2008-04-02 17:47:37.000000000 -0400
> 
> > @@ -187,19 +170,18 @@ Components of Memory Policies
> >  
> >  	MPOL_PREFERRED:  This mode specifies that the allocation should be
> >  	attempted from the single node specified in the policy.  If that
> > -	allocation fails, the kernel will search other nodes, exactly as
> > -	it would for a local allocation that started at the preferred node
> > -	in increasing distance from the preferred node.  "Local" allocation
> > -	policy can be viewed as a Preferred policy that starts at the node
> > +	allocation fails, the kernel will search other nodes, in order of
> > +	increasing distance from the preferred node based on information
> > +	provided by the platform firmware.
> >  	containing the cpu where the allocation takes place.
> 
> Something in the patch lines above seems to be foobarred.
> I.e., the sentences/lines don't flow correctly.

Looks like I forgot to delete the line starting with 'containing ...'.
I'll fix it, along with the 'expecially' in patch 8. [That's not a word,
huh? :)]

Lee

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-04-14 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080404145944.5442.2684.sendpatchset@localhost>
     [not found] ` <20080404150040.5442.49132.sendpatchset@localhost>
2008-04-14 17:23   ` [PATCH 9/15] Mempolicy: Use MPOL_PREFERRED for system-wide default policy Randy Dunlap
2008-04-14 20:05     ` Lee Schermerhorn [this message]
     [not found] ` <20080404150034.5442.92020.sendpatchset@localhost>
2008-04-14 17:32   ` [PATCH 8/15] Mempolicy: Rework mempolicy Reference Counting [yet again] Randy Dunlap

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=1208203520.5453.8.camel@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.whitney@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-numa@vger.kernel.org \
    --cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).