public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Andi Kleen <ak@suse.de>, Henti Smith <bain@tcsn.co.za>,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
	Riley Williams <Riley@Williams.Name>
Subject: Re: [Lse-tech] Re: maximum possible memory limit ..
Date: Mon, 28 Apr 2003 10:16:43 -0700	[thread overview]
Message-ID: <3EAD61FB.30907@us.ibm.com> (raw)
In-Reply-To: 3EAD5D90.7010101@gmx.net

Carl-Daniel Hailfinger wrote:
> Cool. Sorry to be pestering about the 64-bit limits, but can we really
> use 2^64 bytes of memory on ia64/ppc64/x86-64 etc.? (AFAIK, 64-bit
> arches don't suffer from a small ZONE_LOWMEM.)

First of all, I'm not sure any of the 64-bit arches even fully support
64-bit physical addresses.  If I remember correctly the first hammers
support 40 bits, with more to be added later.  Power4 is in close to the
same boat, but I know they go up to 256GB today (I seem to recall
something about 44-bit being the limit, though).

Don't forget that highmem starts to be needed before the 4G boundary.
The kernel has only 1GB of virtual space (look for PAGE_OFFSET, which
defines it), which means that you start needing to pull all of the
highmem trickery before you get to the actual limits.

Nobody knows how far it will go.  It's fairly safe to say that, at this
rate, Linux will keep up with whatever hardware anyone produces.
Unless, of course, someone gets even more perverse than PAE. :)

-- 
Dave Hansen
haveblue@us.ibm.com


  parent reply	other threads:[~2003-04-28 17:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 18:05 maximum possible memory limit Henti Smith
2003-04-24 18:35 ` Valdis.Kletnieks
2003-04-28 13:08 ` Carl-Daniel Hailfinger
2003-04-28 14:10   ` [Lse-tech] " Andi Kleen
2003-04-28 15:11     ` Carl-Daniel Hailfinger
2003-04-28 15:16       ` Andi Kleen
2003-04-28 16:52         ` Dave Hansen
2003-04-28 16:58           ` Martin J. Bligh
2003-04-28 22:40             ` William Lee Irwin III
2003-04-28 23:50               ` Dave Jones
2003-04-29  0:00                 ` William Lee Irwin III
2003-04-29  0:06                   ` Dave Jones
2003-04-29  0:13                     ` William Lee Irwin III
2003-04-28 22:34           ` William Lee Irwin III
2003-04-28 22:33         ` William Lee Irwin III
2003-04-29  4:02         ` William Lee Irwin III
2003-04-28 16:45     ` Dave Hansen
2003-04-28 16:57       ` Carl-Daniel Hailfinger
2003-04-28 17:13         ` Andi Kleen
2003-04-28 17:53           ` David Mosberger
2003-04-28 18:31             ` Gerrit Huizenga
2003-04-28 19:05               ` David Mosberger
2003-04-28 17:16         ` Dave Hansen [this message]
2003-04-28 17:36           ` Carl-Daniel Hailfinger
2003-04-28 17:44             ` Andi Kleen
2003-04-28 22:43             ` William Lee Irwin III
2003-04-28 22:43           ` William Lee Irwin III
2003-04-28 18:57         ` Anton Blanchard
2003-04-28 17:14       ` Andi Kleen
2003-04-28 17:26         ` Dave Hansen

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=3EAD61FB.30907@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=Riley@Williams.Name \
    --cc=ak@suse.de \
    --cc=bain@tcsn.co.za \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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