linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Nishanth Aravamudan <nacc@us.ibm.com>
Subject: Re: [PATCH] Make dynamic/run-time configuration of zonelist order configurable
Date: Thu, 31 May 2007 10:58:43 -0400	[thread overview]
Message-ID: <1180623523.5091.32.camel@localhost> (raw)
In-Reply-To: <20070530130911.431d5f6f.akpm@linux-foundation.org>

On Wed, 2007-05-30 at 13:09 -0700, Andrew Morton wrote:
> On Wed, 30 May 2007 15:42:22 -0400
> Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
> 
> > But, before I go and rework it against the current mm
> > tree and then rebase the hugetlb fix on that, could you offer an opinion
> > either way, whether it's worth the effort and a new Kconfig option to
> > attempt to give back this amount init code/data?  I recall you making
> > noise about the zonelist order patch being "a lot of code" when Kame
> > first posted it.
> 
> The concern with a "lot of code" is 99% about complexity, reliability and
> maintainability and only 1% about RAM usage.

Ah, OK.

> 
> This stuff is mainly a NUMA/SMP thing, isn't it?  If so, a couple of k is
> neither here nor there.

I agree that on the platforms I deal with, it's not an issue.  However,
as I mentioned, I've seen chatter on the lists from folks who apparently
use numa emulation [requires NUMA infrastructure] on single cpu 32-bit
systems as a "poor man's containers" for memory resource management and
didn't want to impose the addtional, admittedly small, extra overhead on
them.  Perhaps this usage goes away when containers becomes mainline.
If no one in that camp complains and you don't think it's worth it, I'll
drop it.

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>

      reply	other threads:[~2007-05-31 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 19:48 Lee Schermerhorn
2007-05-30  2:21 ` KAMEZAWA Hiroyuki
2007-05-30 15:52   ` Lee Schermerhorn
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 [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=1180623523.5091.32.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox