From: Adrian Bunk <bunk@stusta.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, Mark Lord <lkml@rtr.ca>,
Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G
Date: Tue, 12 Jun 2007 03:12:02 +0200 [thread overview]
Message-ID: <20070612011202.GT3588@stusta.de> (raw)
In-Reply-To: <20070612000026.GC6909@holomorphy.com>
On Mon, Jun 11, 2007 at 05:00:26PM -0700, William Lee Irwin III wrote:
> On Thu, Jun 07, 2007 at 07:35:51PM -0700, William Lee Irwin III wrote:
> >> + PAE is required for NX support, and furthermore enables
> >> + larger swapspace support for non-overcommit purposes. It
> >> + has the cost of more pagetable lookup overhead, and also
> >> + consumes more pagetable space per process.
>
> On Tue, Jun 12, 2007 at 01:52:35AM +0200, Adrian Bunk wrote:
> > It's not specific to this help text, but I start becoming a bit picky
> > about this issues:
> > If you understand this help text after reading it, you don't need a help
> > text for this option... ;-)
> > What is "NX support"?
> > What are "non-overcommit purposes"?
> > What is "pagetable lookup overhead"?
> > And if in doubt, should I say Y or N?
> > "System administrator who knows which hardware components he put into
> > the computer and which filesystems his data is on" might be a good
> > description for the average kconfig user, and these are the people who
> > should understand this help text.
>
> I would like to have some place to explain issues such as those, but
> there are as of yet no designated places for tutorial-level information.
>
> If such a place were provided, I would provide storybook commentary to
> explain all those. Similarly actually holds for kernel function docbook.
There's no 4 line limit for Kconfig entries. If it takes a 10 line
paragraph for a short explanation what the NX bit is and when enabling
NX support makes sense (because it will be used) then that's completely
appropriate here. The same goes for the other parts.
The kconfig help should give anyone running "make oldconfig" a rough
understanding what this option is about and a clear understanding what
to answer for this option ("If unsure, say Y/N." is a standard text we
use for the latter).
> -- wli
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-06-12 1:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 2:35 divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G William Lee Irwin III
2007-06-08 2:41 ` Andrew Morton
2007-06-08 3:06 ` William Lee Irwin III
2007-06-08 3:38 ` H. Peter Anvin
2007-06-08 3:41 ` William Lee Irwin III
2007-06-08 3:44 ` H. Peter Anvin
2007-06-08 3:51 ` William Lee Irwin III
2007-06-11 23:52 ` Adrian Bunk
2007-06-12 0:00 ` William Lee Irwin III
2007-06-12 1:12 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-08 8:07 Mikael Pettersson
2007-06-08 14:47 ` William Lee Irwin III
2007-06-12 8:37 linux
2007-06-13 7:26 Bodo Eggert
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=20070612011202.GT3588@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=wli@holomorphy.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