From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Martin Steigerwald <ms@teamix.de>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: physical memory limit of 64-bit linux
Date: Tue, 16 Dec 2008 11:07:20 -0800 [thread overview]
Message-ID: <4947FC68.4020603@goop.org> (raw)
In-Reply-To: <20081216184742.GL11683@elte.hu>
Ingo Molnar wrote:
> phase 3) We could also go close to 47 bits: with various more invasive
> movings of VMALLOC and rest upwards, and other considerations
> such as the elimination of the generous start of 8 TB hole at
> __PAGE_OFFSET - i.e. moving __PAGE_OFFSET straight down to
> minus 128 TB. 120 TB would be doable.
>
Originally it was there, but I moved it up because that's where Xen puts
itself when running a PV 64-bit guest. It is also properly
parameterised now, so we could make it move on the basis of a config
setting.
> phase 4) If the 48 bits limit is ever lifted on the CPU side, we can move
> __PAGE_OFFSET down. This is actually less invasive than phase
> 3), because moving __PAGE_OFFSET is relatively easy. The far
> more invasive change would be the necessary changes to the
> virtual memory code: the current 4-level paging has a 256 TB
> limit which comes from the 512*512*512*512*4K split of
> pgd/pud/pmd/pte entries. Either PGDIR_SHIFT would have to be
> increased, moving the root pgtable's size from 4K to 8K or more,
> or another pgdir level would have to be introduced (which is
> even more intrusive and much less likely to be implemented by hw
> makers).
>
...or we could just reintroduce highmem ;)
J
next prev parent reply other threads:[~2008-12-16 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 14:56 physical memory limit of 64-bit linux Martin Steigerwald
2008-12-16 15:54 ` Rafael J. Wysocki
2008-12-16 16:44 ` Andi Kleen
2008-12-17 14:12 ` Martin Steigerwald
2008-12-16 18:47 ` Ingo Molnar
2008-12-16 19:07 ` Jeremy Fitzhardinge [this message]
2008-12-16 19:23 ` Ingo Molnar
2008-12-16 19:28 ` Andi Kleen
2008-12-17 14:30 ` Martin Steigerwald
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=4947FC68.4020603@goop.org \
--to=jeremy@goop.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ms@teamix.de \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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.