From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, clameter@sgi.com, ak@suse.de
Subject: Re: [PATCH] change global zonelist order on NUMA v2
Date: Fri, 27 Apr 2007 09:41:41 +0900 [thread overview]
Message-ID: <20070427094141.82b16497.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1177624660.5705.72.camel@localhost>
On Thu, 26 Apr 2007 17:57:40 -0400
Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
> On Thu, 2007-04-26 at 18:34 +0900, KAMEZAWA Hiroyuki wrote:
> > Changelog from V1 -> V2
> > - sysctl name is changed to be relaxed_zone_order
> > - NORMAL->NORMAL->....->DMA->DMA->DMA order (new ordering) is now default.
> > NORMAL->DMA->NORMAL->DMA order (old ordering) is optional.
> > - addes boot opttion to set relaxed_zone_order. ia64 is supported now.
> > - Added documentation
> >
> > patch is against 2.6.21-rc7-mm2. tested on ia64 NUMA box. works well.
>
> [PATCH] factor/rework change zonelist order patch
>
> Against 2.6.21-rc7 atop KAMEZAWA Hiroyuki's "change global zonelist
> order on NUMA v2" patch.
>
Hi, this looks 'easier-to-read' than mine. thanks.
> 3) kept early_param() definition for boot parameter in mm/page_alloc.c,
> along with the handler function. One less file to modify.
>
I put early_param() to arch dependent part just beacause no generic code
except for pci seems to call it. If it is allowed, I welcome this change.
> 4) modified the two Documentation additions to match these changes.
>
> I've tested various combinations [non-exhaustive], with an ad hoc
> instrumentation patch, and it appears to work as expected [as I expect,
> anyway] on ia64 NUMA.
>
> Question: do we need to rebuild the zonelist caches when we reorder
> the zones? The z_to_n[] array appears to be dependent on
> the zonelist order...
>
maybe no.
> Also: I see the "Movable" zones show up in 21-rc7-mm2. This patch
> will cause Movable zone to overflow to remote movable zones
> before using local Normal memory in non-default, zone order.
> Is this what we want?
>
>From my point of view, it's what I want. What we have to do will be
establish a way to create ZONE_MOVABLE with suitable size on each node.
I'll merge your change to my set and add "automatic detection" support.
Thank you.
-Kame
--
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>
prev parent reply other threads:[~2007-04-27 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 9:34 KAMEZAWA Hiroyuki
2007-04-26 9:47 ` Andi Kleen
2007-04-26 10:10 ` KAMEZAWA Hiroyuki
2007-04-26 10:53 ` [PATCH] change global zonelist order on NUMA v3 KAMEZAWA Hiroyuki
2007-04-26 16:00 ` Lee Schermerhorn
2007-04-26 16:06 ` Christoph Lameter
2007-04-26 16:29 ` Lee Schermerhorn
2007-04-26 16:36 ` Christoph Lameter
2007-04-26 15:48 ` [PATCH] change global zonelist order on NUMA v2 Christoph Lameter
2007-04-27 0:27 ` KAMEZAWA Hiroyuki
2007-04-27 1:25 ` Christoph Lameter
2007-04-27 1:50 ` KAMEZAWA Hiroyuki
2007-04-30 15:03 ` Lee Schermerhorn
2007-04-30 14:09 ` Lee Schermerhorn
2007-04-26 15:46 ` Christoph Lameter
2007-04-26 15:51 ` Andi Kleen
2007-04-26 21:57 ` Lee Schermerhorn
2007-04-26 22:07 ` Christoph Lameter
2007-04-27 0:41 ` KAMEZAWA Hiroyuki [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=20070427094141.82b16497.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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