From: Bob Liu <lliubbo@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>, Mel Gorman <mel@csn.ul.ie>
Cc: kamezawa.hiroyu@jp.fujitsu.com, minchan.kim@gmail.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
andi@firstfloor.org, rientjes@google.com,
lee.schermerhorn@hp.com
Subject: Re: [PATCH] mempolicy:add GFP_THISNODE when allocing new page
Date: Fri, 16 Apr 2010 09:02:32 +0800 [thread overview]
Message-ID: <r2hcf18f8341004151802g2bc338c0sb1e815c0a14e7474@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1004151939310.17800@router.home>
On Fri, Apr 16, 2010 at 8:41 AM, Christoph Lameter
<cl@linux-foundation.org> wrote:
> On Tue, 13 Apr 2010, Bob Liu wrote:
>
>> If move to the next node instead of early return, the relative position of the
>> page to the beginning of the node set will be break;
>
> Right.
>
Thanks!
Then would you please acking this patch? So as mel.
>> (BTW:I am still not very clear about the preservation of the relative
>> position of the
>> page to the beginning of the node set. I think if the user call
>> migrate_pages() with
>> different count of src and dest nodes, the relative position will also break.
>> eg. if call migrate_pags() from nodes is node(1,2,3) , dest nodes is
>> just node(3).
>> the current code logical will move pages in node 1, 2 to node 3. this case the
>> relative position is breaked).
>
> But in that case the user has specified that the set of nodes should be
> compacted during migration and therefore requested what ocurred.
>
--
Regards,
--Bob
--
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>
next prev parent reply other threads:[~2010-04-16 1:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 2:59 [PATCH] mempolicy:add GFP_THISNODE when allocing new page Bob Liu
2010-04-06 4:33 ` Minchan Kim
2010-04-06 4:56 ` Bob Liu
2010-04-06 5:06 ` Minchan Kim
2010-04-13 8:19 ` KAMEZAWA Hiroyuki
2010-04-13 8:20 ` Bob Liu
2010-04-13 8:38 ` Mel Gorman
2010-04-13 14:28 ` Bob Liu
2010-04-16 0:41 ` Christoph Lameter
2010-04-16 1:02 ` Bob Liu [this message]
2010-04-16 16:02 ` Christoph Lameter
2010-04-16 11:15 ` Mel Gorman
2010-04-16 15:03 ` Bob Liu
2010-04-16 15:55 ` Christoph Lameter
2010-04-17 13:54 ` Bob Liu
2010-04-19 17:47 ` Christoph Lameter
2010-04-20 2:08 ` Bob Liu
2010-04-21 14:13 ` Christoph Lameter
2010-04-22 1:03 ` Bob Liu
2010-04-22 14:38 ` Christoph Lameter
2010-04-13 8:27 ` Minchan Kim
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=r2hcf18f8341004151802g2bc338c0sb1e815c0a14e7474@mail.gmail.com \
--to=lliubbo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.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).