From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, nacc@us.ibm.com
Subject: Re: [PATCH] Make dynamic/run-time configuration of zonelist order configurable
Date: Wed, 30 May 2007 11:52:01 -0400 [thread overview]
Message-ID: <1180540321.5850.6.camel@localhost> (raw)
In-Reply-To: <20070530112119.efa977fe.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 2007-05-30 at 11:21 +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 29 May 2007 15:48:41 -0400
> Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
>
> > Signed-off-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
> >
>
> no problem was found on my ia64 test box.
>
> But one point..
>
> > -#ifdef CONFIG_NUMA
> > +#ifdef CONFIG_DYNAMIC_ZONELIST_ORDER
> > {
> > .ctl_name = CTL_UNNUMBERED,
> > .procname = "numa_zonelist_order",
>
> non-NUMA, memory-hotpluggable machine need this control ??
>
Hi, Kame:
Here was my thinking on that point--actually on the numa_zonelist_order
sysctl in general:
When would it ever be needed? I think the answer is when the dynamic
configuration didn't "get it right" and you want to fix it w/o reboot.
I agree that it is very likely that you wouldn't want to reboot if
you've gone to all the trouble to support memory hotplug. In that case,
we have a couple of choices:
1) just enable the config option manually for platforms that support
memory hotplug, or
2) make the option default to 'y' when memory hotplug is configured.
As I tried to indicate in the patch description, because some smallish
systems appear to use NUMA emulation for resource management, they must
enable NUMA support. However, they may not [I think probably not] need
run-time zoneorder configuration. I suspect those platforms don't
support memory hotplug at this time either. Now, the code in question
[sysctl and build_zonelist functions] may be relatively small--i.e.,
less than a page. But, it all adds up, so I offered a way for small
systems that still wanted NUMA support to get back what we took from
them with the zonelist order patches.
Thoughts?
Lee
--
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:[~2007-05-30 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 19:48 [PATCH] Make dynamic/run-time configuration of zonelist order configurable Lee Schermerhorn
2007-05-30 2:21 ` KAMEZAWA Hiroyuki
2007-05-30 15:52 ` Lee Schermerhorn [this message]
2007-05-31 12:34 ` KAMEZAWA Hiroyuki
2007-05-31 17:08 ` Lee Schermerhorn
2007-05-30 18:12 ` Andrew Morton
2007-05-30 19:42 ` Lee Schermerhorn
2007-05-30 20:09 ` Andrew Morton
2007-05-31 14:58 ` Lee Schermerhorn
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=1180540321.5850.6.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.