linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: 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, 13 Apr 2010 17:19:03 +0900	[thread overview]
Message-ID: <20100413171903.ea4d8215.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1270522777-9216-1-git-send-email-lliubbo@gmail.com>

On Tue,  6 Apr 2010 10:59:37 +0800
Bob Liu <lliubbo@gmail.com> wrote:

> In funtion migrate_pages(), if the dest node have no
> enough free pages,it will fallback to other nodes.
> Add GFP_THISNODE to avoid this, the same as what
> funtion new_page_node() do in migrate.c.
> 
> Signed-off-by: Bob Liu <lliubbo@gmail.com>

Reviewd-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>


> ---
>  mm/mempolicy.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index 08f40a2..fc5ddf5 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -842,7 +842,8 @@ static void migrate_page_add(struct page *page, struct list_head *pagelist,
>  
>  static struct page *new_node_page(struct page *page, unsigned long node, int **x)
>  {
> -	return alloc_pages_exact_node(node, GFP_HIGHUSER_MOVABLE, 0);
> +	return alloc_pages_exact_node(node,
> +				GFP_HIGHUSER_MOVABLE | GFP_THISNODE, 0);
>  }
>  
>  /*
> -- 
> 1.5.6.3
> 
> --
> 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>
> 

--
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>

  parent reply	other threads:[~2010-04-13  8:22 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 [this message]
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
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=20100413171903.ea4d8215.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@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