linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <cl@linux.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, npiggin@suse.de,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] Use integer fields lookup for gfp_zone and check for errors in flags passed to the page allocator
Date: Wed, 27 May 2009 00:26:20 +0100	[thread overview]
Message-ID: <20090526232620.GA6189@csn.ul.ie> (raw)
In-Reply-To: <alpine.DEB.1.10.0905261401100.5632@gentwo.org>

On Tue, May 26, 2009 at 02:04:35PM -0400, Christoph Lameter wrote:
> On Mon, 25 May 2009, Mel Gorman wrote:
> 
> > I expect that the machine would start running into reclaim issues with
> > enough uptime because it'll not be using Highmem as it should. Similarly,
> > the GFP_DMA32 may also be a problem as the new implementation is going
> > ZONE_DMA when ZONE_NORMAL would have been ok in this case.
> 
> Right. The fallback for DMA32 is wrong. Should fall back to ZONE_NORMAL.
> Not to DMA. And the config variable to check for highmem was wrong.
> 

That fixed things right up on x86 at least and it looks good. I've queued
up a few tests with the patch applied on x86, x86-64 and ppc64. Hopefully
it'll go smoothly.

For your patch + fix merged

Acked-by: Mel Gorman <mel@csn.ul.ie>

> 
> Subject: Fix gfp zone patch
> 
> 1. If there is no DMA32 fall back to NORMAL instead of DMA
> 
> 2. Use the correct config variable for HIGHMEM
> 
> Signed-off-by: Christoph Lameter <cl@linux-foundation.org>
> 
> 
> ---
>  include/linux/gfp.h |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6/include/linux/gfp.h
> ===================================================================
> --- linux-2.6.orig/include/linux/gfp.h	2009-05-26 12:59:19.000000000 -0500
> +++ linux-2.6/include/linux/gfp.h	2009-05-26 12:59:31.000000000 -0500
> @@ -112,7 +112,7 @@ static inline int allocflags_to_migratet
>  		((gfp_flags & __GFP_RECLAIMABLE) != 0);
>  }
> 
> -#ifdef CONFIG_ZONE_HIGHMEM
> +#ifdef CONFIG_HIGHMEM
>  #define OPT_ZONE_HIGHMEM ZONE_HIGHMEM
>  #else
>  #define OPT_ZONE_HIGHMEM ZONE_NORMAL
> @@ -127,7 +127,7 @@ static inline int allocflags_to_migratet
>  #ifdef CONFIG_ZONE_DMA32
>  #define OPT_ZONE_DMA32 ZONE_DMA32
>  #else
> -#define OPT_ZONE_DMA32 OPT_ZONE_DMA
> +#define OPT_ZONE_DMA32 ZONE_NORMAL
>  #endif
> 
>  /*
> 

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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:[~2009-05-26 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 18:42 Christoph Lameter
2009-05-25  1:51 ` KAMEZAWA Hiroyuki
2009-05-26 16:58   ` Christoph Lameter
2009-05-25 11:30 ` Mel Gorman
2009-05-26 18:04   ` Christoph Lameter
2009-05-26 23:26     ` Mel Gorman [this message]
2009-05-27  9:48       ` Mel Gorman
2009-05-27 14:23         ` Christoph Lameter

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=20090526232620.GA6189@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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