linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bob Liu <lliubbo@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
	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: Tue, 20 Apr 2010 10:08:26 +0800	[thread overview]
Message-ID: <w2ucf18f8341004191908v2546cfffo3cc7615802ca1c80@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1004191245250.9855@router.home>

On Tue, Apr 20, 2010 at 1:47 AM, Christoph Lameter
<cl@linux-foundation.org> wrote:
> On Sat, 17 Apr 2010, Bob Liu wrote:
>
>> > GFP_THISNODE forces allocation from the node. Without it we will fallback.
>> >
>>
>> Yeah, but I think we shouldn't fallback at this case, what we want is
>> alloc a page
>> from exactly the dest node during migrate_to_node(dest).So I added
>> GFP_THISNODE.
>
> Why would we want that?
>

Because if dest node have no memory, it will fallback to other nodes.
The dest node's fallback nodes may be nodes in nodemask from_nodes.
It maybe make circulation ?.(I am not sure.)

What's more,i think it against the user's request.
The user wants to move pages from from_nodes to to_nodes, if fallback
happened, the pages may be moved to other nodes instead of any node in
nodemask to_nodes.
I am not sure if the user can expect this and accept.

Thanks a lot for your patient reply. :)
-- 
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>

  reply	other threads:[~2010-04-20  2:08 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
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 [this message]
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=w2ucf18f8341004191908v2546cfffo3cc7615802ca1c80@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).