From: Andi Kleen <ak@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, yogyas@gmail.com
Subject: Re: How much kernel memory is in 64-bit OS ?
Date: 18 Sep 2006 10:31:21 +0200 [thread overview]
Message-ID: <p73odtd4luu.fsf@verdi.suse.de> (raw)
In-Reply-To: <450DE3DE.50301@redhat.com>
Rik van Riel <riel@redhat.com> writes:
>
> However, all 64 bit architectures have one thing in common.
> There is so much address space available for both kernel and
> userspace that we won't have to worry about a shortage for a
> very long time.
Nearly.
The x86-64 port started off with a 512GB user space VM limit, and then
that later was extended with 4 level page tables because it wasn't
quite enough for everybody.
-Andi
next prev parent reply other threads:[~2006-09-18 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 11:34 How much kernel memory is in 64-bit OS ? yogeshwar sonawane
2006-09-18 0:10 ` Rik van Riel
2006-09-18 8:31 ` Andi Kleen [this message]
2006-09-18 8:35 ` Jan Engelhardt
2006-09-18 12:30 ` Rik van Riel
2006-09-18 12:34 ` Jan Engelhardt
2006-09-18 13:30 ` Kyle Moffett
2006-09-18 9:51 ` yogeshwar sonawane
2006-09-18 13:39 ` Helge Hafting
2006-09-18 17:22 ` Andi Kleen
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=p73odtd4luu.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=yogyas@gmail.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