From: Theodore Tso <tytso@mit.edu>
To: thunder7@xs4all.nl
Cc: Arjan van de Ven <arjan@infradead.org>,
Franck Pommereau <pommereau@univ-paris12.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options
Date: Thu, 14 Dec 2006 10:37:54 -0500 [thread overview]
Message-ID: <20061214153754.GD9079@thunk.org> (raw)
In-Reply-To: <20061214152721.GA5652@amd64.of.nowhere>
> + 1 Gigabyte or more total physical RAM, answer "off" here.
>
I don't think your proposed wording (1 gigabyte or more) versus (more
than 1 gigabyte) doesn't really change the sense of this.
If we want to be even more explicit about this, then if the CPU level
selected by the user is greater than Pentium-M (or whatever is was the
oldest CPU that didn't have NX support --- Arjan?) we shouldn't offer
this choice at all, and force CONFIG_HIGHMEM64G. We can give the user
a choice if CONFIG_EMBEDDED is enabled, but otherwise, if the CPU
level is new enough, I think we can safely make the argument that for
nearly all systems, they have enough memory and speed that perhaps we
should just simply always use HIGHMEM64G.
- Ted
next prev parent reply other threads:[~2006-12-14 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 9:26 Executability of the stack Franck Pommereau
2006-12-14 9:57 ` Arjan van de Ven
2006-12-14 12:07 ` Franck Pommereau
2006-12-14 12:19 ` Arjan van de Ven
2006-12-14 15:17 ` [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options Theodore Tso
2006-12-14 15:27 ` thunder7
2006-12-14 15:37 ` Theodore Tso [this message]
2006-12-14 16:06 ` Arjan van de Ven
2006-12-14 16:11 ` Avi Kivity
2006-12-14 19:58 ` Alistair John Strachan
2006-12-15 17:06 ` Bill Davidsen
2006-12-14 15:52 ` Arjan van de Ven
2006-12-14 12:36 ` Executability of the stack James Courtier-Dutton
[not found] ` <1166099950.27217.1024.camel@laptopd505.fenrus.org>
2006-12-14 14:55 ` Franck Pommereau
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=20061214153754.GD9079@thunk.org \
--to=tytso@mit.edu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pommereau@univ-paris12.fr \
--cc=thunder7@xs4all.nl \
/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.