From: Roman Zippel <zippel@linux-m68k.org>
To: Dave Hansen <haveblue@us.ibm.com>
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: Thu, 7 Apr 2005 02:30:00 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0504070219160.15339@scrub.home> (raw)
In-Reply-To: <1112831857.14584.43.camel@localhost>
Hi,
On Wed, 6 Apr 2005, Dave Hansen wrote:
> > 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
I was hoping for this too, in the meantime can't you simply make it a
suboption of DISCONTIGMEM? So an extra option is only visible when it's
enabled and most people can ignore it completely by just disabling a
single option.
> > 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.
Some basic explanation with a link for more information can't hurt.
bye, Roman
--
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>
next prev parent reply other threads:[~2005-04-07 0:30 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
2005-04-07 0:30 ` Roman Zippel [this message]
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=Pine.LNX.4.61.0504070219160.15339@scrub.home \
--to=zippel@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.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