From: William Lee Irwin III <wli@holomorphy.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Mark Lord <lkml@rtr.ca>,
Andi Kleen <ak@suse.de>
Subject: Re: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G
Date: Thu, 7 Jun 2007 20:41:21 -0700 [thread overview]
Message-ID: <20070608034121.GX6909@holomorphy.com> (raw)
In-Reply-To: <4668CF2E.8000707@zytor.com>
William Lee Irwin III wrote:
>> !CONFIG_X86_PAE && CONFIG_HIGHMEM64G doesn't make sense and is not allowed
>> by this patch. CONFIG_X86_PAE && !CONFIG_HIGHMEM64G works here.
On Thu, Jun 07, 2007 at 08:38:22PM -0700, H. Peter Anvin wrote:
> But what's the point?
> If you're going to divorce these, at least do it in a way that makes
> sense, specifically the two independent variables are PAE and HIGHMEM.
> PAE and !HIGHMEM does make (some amount of) sense, due to no kmap overhead.
Beg your pardon? Are you reading the patch description correctly?
-- wli
next prev parent reply other threads:[~2007-06-08 3:41 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 [this message]
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
-- 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=20070608034121.GX6909@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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.