From: Anton Blanchard <anton@samba.org>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Dave Hansen <haveblue@us.ibm.com>, 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: Tue, 29 Apr 2003 04:57:41 +1000 [thread overview]
Message-ID: <20030428185741.GA14391@krispykreme> (raw)
In-Reply-To: <3EAD5D90.7010101@gmx.net>
Hi,
> 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.)
For ppc64 our current maximum is 2TB and so far the biggest machine we
have tested on is 512GB.
Anton
next prev parent reply other threads:[~2003-04-28 18:49 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
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 [this message]
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=20030428185741.GA14391@krispykreme \
--to=anton@samba.org \
--cc=Riley@Williams.Name \
--cc=ak@suse.de \
--cc=bain@tcsn.co.za \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=haveblue@us.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).