public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Henti Smith <bain@tcsn.co.za>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: maximum possible memory limit ..
Date: Mon, 28 Apr 2003 15:08:02 +0200	[thread overview]
Message-ID: <3EAD27B2.9010807@gmx.net> (raw)
In-Reply-To: <20030424200524.5030a86b.bain@tcsn.co.za>

[CC:ing lse-tech because they know better than me]

Henti Smith wrote:
> Hi all 
> 
> I had a discussion with somebody watching the whole M$ server launch and mentioned then new systems supports up to a terabyte of ram. 
> I've tried looking for a hint at what the max memory support on linux is and cannot find it anywhere.
> 
> can somebody here enlighten me on just what the maximum amount of memory linux can deal with ? 

Linux supports up to 4 GB (~2^32 bytes) of memory on 32-bit
architectures and 64 GB (~2^36 bytes) on x86 with PAE. No other
operating system can support more on 32-bit since it is a limitation of
the hardware.
On 64-bit systems, Linux supports up to 16 EB (~2^64 bytes) of memory,
which is about 16 million times more than the 1 TB limit of MS.

Current Linux 2.4 allows 32 CPUs for 32-bit arches and 64 CPUs on 64-bit
arches. However, this limit is (was?) being removed in 2.5, so you can
have up to 32767 CPUs, which should be enough for you right now.
(Note: I said _right now_, lest anybody make jokes about 640K limit)


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


  parent reply	other threads:[~2003-04-28 12:55 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 [this message]
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
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=3EAD27B2.9010807@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=bain@tcsn.co.za \
    --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