linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH 1/4] create mm/Kconfig for arch-independent memory options
Date: Wed, 06 Apr 2005 16:57:36 -0700	[thread overview]
Message-ID: <1112831857.14584.43.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0504070133380.25131@scrub.home>

On Thu, 2005-04-07 at 01:40 +0200, Roman Zippel wrote:
> On Wed, 6 Apr 2005, Dave Hansen wrote:
> > On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
> > > Dave Hansen wrote:
> > > > --- memhotplug/mm/Kconfig~A6-mm-Kconfig	2005-04-04 09:04:48.000000000 -0700
> > > > +++ memhotplug-dave/mm/Kconfig	2005-04-04 10:15:23.000000000 -0700
> > > > @@ -0,0 +1,25 @@
> > > > +choice
> > > > +	prompt "Memory model"
> > > > +	default FLATMEM
> > > > +	default SPARSEMEM if ARCH_SPARSEMEM_DEFAULT
> > > > +	default DISCONTIGMEM if ARCH_DISCONTIGMEM_DEFAULT
> > > 
> > > Does this really have to be a user visible option and can't it be
> > > derived from other values? The help text entries are really no help at all.
> > 
> > I hope that this selection will replace the current DISCONTIGMEM prompts
> > in the individual architectures.  That way, you won't get a net increase
> > in the number of prompts.
> 
> Why is this choice needed at all? Why would one choose SPARSEMEM over 
> DISCONTIGMEM?

For now, it's only so people can test either one, and we don't have to
try to toss DICONTIGMEM out of the kernel in fell swoop.  When the
memory hotplug options are enabled, the DISCONTIG option goes away, and
SPARSEMEM is selected as the only option.

I hope to, in the future, make the options more like this:

config MEMORY_HOTPLUG...
config NUMA...

config DISCONTIGMEM
	depends on NUMA && !MEMORY_HOTPLUG

config SPARSEMEM
	depends on MEMORY_HOTPLUG || OTHER_ARCH_THING

config FLATMEM
	depends on !DISCONTIGMEM && !SPARSEMEM

So, if they enable NUMA, they get DISCONTIGMEM automatically.  If they
enable MEMORY_HOTPLUG on top of that, they automatically get SPARSEMEM
instead.  All of the complex "pick your memory model" stuff goes away,
and you just select features.  However, I think the current situation is
a reasonable intermediate step, as we need to be able to switch back and
forth for now.

> Help texts such as "If unsure, choose <something else>" make 
> the complete config option pretty useless.

They don't make it useless, they just guide a clueless user to the right
place, without them having to think about it at all.  Those of us that
need to test the various configurations are quite sure of what we're
doing, and can ignore the messages. :)

I'm not opposed to creating some better help text for those things, I'm
just not sure that we really need it, or that it will help end users get
to the right place.  I guess more explanation never hurt anyone.

-- Dave

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-04-06 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 17:50 Dave Hansen
2005-04-04 23:22 ` Mike Kravetz
2005-04-04 23:29   ` Dave Hansen
2005-04-06 20:58 ` Roman Zippel
2005-04-06 21:01   ` Dave Hansen
2005-04-06 23:40     ` Roman Zippel
2005-04-06 23:57       ` Dave Hansen [this message]
2005-04-07  0:30         ` Roman Zippel
2005-04-07 15:30           ` Dave Hansen
2005-04-07 16:36           ` Dave Hansen

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=1112831857.14584.43.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zippel@linux-m68k.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