From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: "3.5GB user address space" option.
Date: 17 Oct 2001 21:38:35 -0700 [thread overview]
Message-ID: <9qlmcb$4h4$1@cesium.transmeta.com> (raw)
In-Reply-To: <1981072193242.20011018021819@spylog.com>
Followup to: <1981072193242.20011018021819@spylog.com>
By author: "Oleg A. Yurlov" <kris@spylog.com>
In newsgroup: linux.dev.kernel
>
>
> Hi, folks,
>
> How I can use 3.5GB in my apps ? I try malloc() and get error on 2G
> bounce... :-(
>
> Hardware - SMP server, 2Gb RAM, 8Gb swap, kernel 2.4.12aa1.
>
Get a 64-bit CPU. You're running into a fundamental limit of 32-bit
architectures.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-10-18 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 22:18 "3.5GB user address space" option Oleg A. Yurlov
2001-10-17 22:27 ` Rik van Riel
2001-10-18 4:38 ` H. Peter Anvin [this message]
2001-10-18 9:09 ` Andrea Arcangeli
2001-10-18 13:47 ` Re[2]: " Oleg A. Yurlov
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='9qlmcb$4h4$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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