linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>, Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [1/3] Add __GFP_THISNODE to avoid fallback to other nodes and ignore cpuset/memory policy restrictions.
Date: Fri, 11 Aug 2006 14:41:34 -0500	[thread overview]
Message-ID: <200608111441.34648.dmccr@us.ibm.com> (raw)
In-Reply-To: <20060811114243.49fa4390.akpm@osdl.org>

On Friday 11 August 2006 1:42 pm, Andrew Morton wrote:
> How about we do
>
> /*
>  * We do this to avoid lots of ifdefs and their consequential conditional
>  * compilation
>  */
> #ifdef CONFIG_NUMA
> #define NUMA_BUILD 1
> #else
> #define NUMA_BUILD 0
> #endif
>
> Then we can do
>
> --- a/mm/page_alloc.c~a
> +++ a/mm/page_alloc.c
> @@ -903,7 +903,7 @@ get_page_from_freelist(gfp_t gfp_mask, u
>          */
>         do {
>                 zone = *z;
> -               if (unlikely((gfp_mask & __GFP_THISNODE) &&
> +               if (NUMA_BUILD && unlikely((gfp_mask & __GFP_THISNODE) &&
>                         zone->zone_pgdat !=
> zonelist->zones[0]->zone_pgdat)) break;
>                 if ((alloc_flags & ALLOC_CPUSET) &&
> _

Wouldn't you get a similar effect by doing

#ifdef CONFIG_NUMA
#define	gfp_thisnode(__mask)		((__mask) & __GFP_THISNODE)
#else
#define	gfp_thisnode(__mask)		(0)

Or are there too many different ways this is used to make a macro practical?  
What am I missing here?

Dave McCracken

--
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:[~2006-08-11 19:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 16:33 Christoph Lameter
2006-08-08 16:34 ` [2/3] sys_move_pages: Do not fall back to other nodes Christoph Lameter
2006-08-08 16:37   ` [3/3] Guarantee that the uncached allocator gets pages on the correct node Christoph Lameter
2006-08-08 16:56 ` [1/3] Add __GFP_THISNODE to avoid fallback to other nodes and ignore cpuset/memory policy restrictions Andy Whitcroft
2006-08-08 17:01   ` Christoph Lameter
2006-08-08 16:59 ` Mel Gorman
2006-08-08 17:03   ` Christoph Lameter
2006-08-08 17:16     ` Mel Gorman
2006-08-08 17:51       ` Christoph Lameter
2006-08-08 17:47     ` Paul Jackson
2006-08-08 17:59       ` Christoph Lameter
2006-08-08 18:18         ` Paul Jackson
2006-08-08 18:49           ` Christoph Lameter
2006-08-08 20:35             ` Paul Jackson
2006-08-09  9:33               ` Mel Gorman
2006-08-09  1:34 ` KAMEZAWA Hiroyuki
2006-08-09  2:00   ` Christoph Lameter
2006-08-10 19:41 ` Andrew Morton
2006-08-11  3:16   ` Christoph Lameter
2006-08-11 18:08     ` Andrew Morton
2006-08-11 18:15       ` Christoph Lameter
2006-08-11 18:42         ` Andrew Morton
2006-08-11 18:51           ` Christoph Lameter
2006-08-11 19:15             ` Andrew Morton
2006-08-11 19:16               ` Christoph Lameter
2006-08-11 19:41           ` Dave McCracken [this message]

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=200608111441.34648.dmccr@us.ibm.com \
    --to=dmccr@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    /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