From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Barry Wu <wqb123@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Can linux support ccNUMA machine now?
Date: Wed, 23 Jan 2002 20:04:05 -0800 [thread overview]
Message-ID: <20020123200405.D899@holomorphy.com> (raw)
In-Reply-To: <20020123003530.60778.qmail@web13903.mail.yahoo.com> <74750000.1011782724@flay>
In-Reply-To: <74750000.1011782724@flay>; from Martin.Bligh@us.ibm.com on Wed, Jan 23, 2002 at 02:45:24AM -0800
At some point in the past, someone wrote:
>> How mcuh memory linux support? 64GB or more?
On Wed, Jan 23, 2002 at 02:45:24AM -0800, Martin J. Bligh wrote:
> Theoritically 64Gb on 32 bit machines, in practice
> significantly less than that (IIRC, something like
> 25-30Gb). It's not terribly efficient in using it though ;-)
With some simple calculations for various things, I predict ZONE_NORMAL
will get filled by large boot-time allocations on x86 with PAE and 64GB
of RAM. I'm not entirely sure what other sorts of pathologies arise
while these beasts still function; but without enough ZONE_NORMAL to
satisfy all the combined boot-time allocation requests, the kernel
will surely panic.
The sizes of these boot-time allocations are not entirely constant
across kernel versions, but there should be some threshhold of
memory size at which any given Linux version to date drops dead on
large memory x86 machines.
On 64-bit machines, there is obviously no such behavior, and Linux
will be able to use the full memory capacity of the system.
Cheers,
Bill
P.S.: Blame it on struct page.
next prev parent reply other threads:[~2002-01-24 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 0:35 Can linux support ccNUMA machine now? Barry Wu
2002-01-23 10:45 ` Martin J. Bligh
2002-01-24 4:04 ` William Lee Irwin III [this message]
2002-01-24 16:15 ` Denis Vlasenko
2002-01-24 18:50 ` William Lee Irwin III
2002-01-24 19:19 ` Andreas Dilger
2002-01-24 20:48 ` William Lee Irwin III
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=20020123200405.D899@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wqb123@yahoo.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