From: Christoph Lameter <cl@linux-foundation.org>
To: Bob Liu <lliubbo@gmail.com>
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: Thu, 22 Apr 2010 09:38:43 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1004220936100.31660@router.home> (raw)
In-Reply-To: <m2vcf18f8341004211803x1392ee7ftc92a1d803316bcee@mail.gmail.com>
On Thu, 22 Apr 2010, Bob Liu wrote:
> Just one small point, why do_move_pages() in migrate.c needs GFP_THISNODE ?
Because the move_pages function call allows the user explicitly specify
the node for each page. If we cannot move the page to the node the user
wants then the best fallback is to keep it where it was.
--
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-22 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 2:59 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
2010-04-21 14:13 ` Christoph Lameter
2010-04-22 1:03 ` Bob Liu
2010-04-22 14:38 ` Christoph Lameter [this message]
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=alpine.DEB.2.00.1004220936100.31660@router.home \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--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