From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sonnyrao@chromium.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: IO regression after ab8fabd46f on x86 kernels with high memory
Date: Wed, 08 May 2013 12:10:25 -0700 [thread overview]
Message-ID: <518AA321.6070900@zytor.com> (raw)
In-Reply-To: <CA+55aFxcq44JsrrR5KKuT=DZQHCfOE3KHQrcD215T+deYesW2g@mail.gmail.com>
On 04/29/2013 03:03 PM, Linus Torvalds wrote:
> On Mon, Apr 29, 2013 at 2:53 PM, Pierre-Loup A. Griffais
> <pgriffais@valvesoftware.com> wrote:
>>
>> Other than this particular concern, what's the high-level take-away? Is PAE
>> support in the Linux kernel a false promise than distros should not be
>> shipping by default, if at all? Should it be removed from the kernel
>> entirely if these configurations are knowingly broken by commits like this?
>
> PAE is "make it barely work". The whole concept is fundamentally
> flawed, and anybody who runs a 32-bit kernel with 16GB or RAM doesn't
> even understand *how* flawed and stupid that is.
>
Let's be straight... the problem isn't PAE per se, the problem is
*HIGHMEM*. PAE just allows HIGHMEM to stretch further into problematic
territory.
Distros install PAE kernels by default because it is required to support
NX. That is fine.
The problem is that once your memory crosses the HIGHMEM threshold
-- 896 MiB in the normal configuration -- then you are in "this is going
to hurt" territory. I have seen HIGHMEM devastate performance without
even crossing the 4 GiB threshold where PAE is required.
We kernel guys have been asking the distros to ship 64-bit kernels even
in their 32-bit distros for many years, but concerns of compat issues
and the desire to deprecate 32-bit userspace seems to have kept that
from happening.
-hpa
next prev parent reply other threads:[~2013-05-08 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:44 IO regression after ab8fabd46f on x86 kernels with high memory Pierre-Loup A. Griffais
2013-04-27 1:53 ` Rik van Riel
2013-04-27 2:42 ` Johannes Weiner
2013-04-29 21:53 ` Pierre-Loup A. Griffais
2013-04-29 22:03 ` Linus Torvalds
2013-04-29 22:08 ` Pierre-Loup A. Griffais
2013-05-02 4:37 ` Sonny Rao
2013-04-30 0:48 ` Rik van Riel
2013-04-30 1:06 ` Pierre-Loup A. Griffais
2013-05-02 1:34 ` Steven Rostedt
2013-05-02 2:46 ` [PATCH] mm,x86: limit 32 bit kernel to 12GB memory Rik van Riel
2013-05-02 7:37 ` Pierre-Loup A. Griffais
2013-05-02 20:03 ` Linus Torvalds
2013-05-11 9:16 ` Yuhong Bao
2013-05-08 19:10 ` H. Peter Anvin [this message]
2013-06-03 1:17 ` IO regression after ab8fabd46f on x86 kernels with high memory Yuhong Bao
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=518AA321.6070900@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgriffais@valvesoftware.com \
--cc=riel@redhat.com \
--cc=sonnyrao@chromium.org \
--cc=torvalds@linux-foundation.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