From: Robert Love <rml@tech9.net>
To: tchiwam <tchiwam@ees2.oulu.fi>
Cc: linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>,
Gerrit Huizenga <gh@us.ibm.com>,
Clifford White <ctwhite@us.ibm.com>,
oliendm@us.ibm.com
Subject: Re: x86 question: Can a process have > 3GB memory?
Date: 09 May 2002 14:40:10 -0700 [thread overview]
Message-ID: <1020980411.880.93.camel@summit> (raw)
In-Reply-To: <Pine.LNX.4.44.0205100020140.31628-100000@st0>
On Thu, 2002-05-09 at 14:24, tchiwam wrote:
> How about other architectures ? like PowerPc.
> Last calculation I did used 11GB of ram (no swap) on a big Number
> Muncher... Would it be nice to use the same code for testing on 32
> architectures with swap ?
All 32-bit architectures have a 4GB address space, 64-bit architectures
obviously have a much bigger one (depends on the arch how many bits are
used for the address space).
PPC obviously does not have the dumb physical memory limitations x86
has, however.
Anyhow, Rik's mmap trick will work on any arch, not just x86.
Robert Love
next prev parent reply other threads:[~2002-05-09 21:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 23:03 x86 question: Can a process have > 3GB memory? Clifford White
2002-05-07 23:08 ` Robert Love
2002-05-08 5:33 ` Martin J. Bligh
2002-05-08 8:29 ` Andrea Arcangeli
2002-05-08 16:21 ` Robert Love
2002-05-07 23:33 ` Alan Cox
2002-05-08 16:54 ` Bill Davidsen
2002-05-08 0:16 ` Gerrit Huizenga
2002-05-08 0:56 ` Rik van Riel
2002-05-08 15:12 ` Martin J. Bligh
2002-05-08 15:17 ` Rik van Riel
2002-05-08 15:24 ` Andi Kleen
2002-05-09 21:24 ` tchiwam
2002-05-09 21:40 ` Robert Love [this message]
2002-05-09 23:56 ` Albert D. Cahalan
2002-05-10 6:58 ` Anton Blanchard
2002-05-10 19:07 ` Bill Davidsen
2002-05-10 19:42 ` Alan Cox
2002-05-10 19:41 ` Linus Torvalds
2002-05-08 8:22 ` Luigi Genoni
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=1020980411.880.93.camel@summit \
--to=rml@tech9.net \
--cc=ctwhite@us.ibm.com \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliendm@us.ibm.com \
--cc=riel@conectiva.com.br \
--cc=tchiwam@ees2.oulu.fi \
/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