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

> 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

That's far too optimistic. 64GB will need patches, like the pgcl 
patch. It is unlikely to work out of the box. Just do the math.

900MB low mem for all the kernel data structures on IA32.

44 byte struct page for each 4K page. This gives 704MB just
for the mem_map array. Leaves you 196MB left for the kernel to 
manage your 64GB of memory and your processes. Unlikely to work.

2.5 uses 40 bytes for an struct page, but that doesn't help much.

Yes you can move the kernel:user split to give the kernel more memory
at the expense of the application, but that is likely to not make the 
user programs happy and also helps only very limited 
(even 2GB lowmem are probably not enough to make it run well with 64GB)

Realistic limit currently is ~16GB with an IA32 box.  For more you need
an 64bit architecture.

-Andi


  reply	other threads:[~2003-04-28 13:58 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   ` Andi Kleen [this message]
2003-04-28 15:11     ` [Lse-tech] " 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=20030428141023.GC4525@Wotan.suse.de \
    --to=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