From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Ed Sweetman <ed.sweetman@wmich.edu>,
Nick Piggin <piggin@cyberone.com.au>,
Donald Maner <donjr@maner.org>, Raul Miller <moth@magenta.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
Date: Wed, 10 Dec 2003 23:19:37 -0800 [thread overview]
Message-ID: <20031211071937.GA8039@holomorphy.com> (raw)
In-Reply-To: <1289530000.1071126517@[10.10.2.4]>
William Lee Irwin III <wli@holomorphy.com> wrote:
>> You're probably thinking of 2:2 split patches.
>> 2:2 splits are at least technically ABI violations, which is probably
>> why this isn't merged etc. Applications sensitive to it are uncommon.
>> Yes, the SVR4 i386 ELF/ABI spec literally mandates 0xC0000000 as the
>> top of the process address space.
On Wed, Dec 10, 2003 at 11:08:38PM -0800, Martin J. Bligh wrote:
> You mean like we place the stack in the "ABI compliant place"?
> Yeah, right ;-)
No specific address is ever cited as a requirement for stack placement;
stack immediately below text is merely given as a "typical arrangement".
i.e. "Although applications may control their memory assignments, the
typical arrangement appears below: [diagram and other bits]" It then
goes on to say, "Processes, therefore, shount _not_ depend on finding
their stack at a particular virtual address."
The process address space boundary is, however, stated as a requirement:
"the reserved area shall not consume more than 1GB of the address space."
-- wli
next prev parent reply other threads:[~2003-12-11 7:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 5:06 PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram Donald Maner
2003-12-11 5:13 ` Nick Piggin
2003-12-11 5:33 ` Ed Sweetman
2003-12-11 5:41 ` William Lee Irwin III
2003-12-11 5:48 ` Roland Dreier
2003-12-11 5:50 ` William Lee Irwin III
2003-12-11 5:48 ` Nick Piggin
2003-12-11 6:01 ` Raul Miller
2003-12-11 6:12 ` Nick Piggin
2003-12-11 6:30 ` David Lang
2003-12-11 7:08 ` Martin J. Bligh
2003-12-11 7:19 ` William Lee Irwin III [this message]
2003-12-11 7:22 ` Martin J. Bligh
2003-12-11 13:24 ` William Lee Irwin III
2003-12-11 14:41 ` Raul Miller
2003-12-11 14:53 ` Raul Miller
2003-12-11 15:00 ` William Lee Irwin III
2003-12-11 16:17 ` moth
2003-12-11 16:35 ` William Lee Irwin III
2003-12-11 19:26 ` Where did the ELF spec go? (SCO website?) Rob Landley
2003-12-11 19:44 ` William Lee Irwin III
2003-12-11 20:25 ` Richard B. Johnson
2003-12-12 11:11 ` Johannes Stezenbach
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 4:51 PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram Raul Miller
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=20031211071937.GA8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=donjr@maner.org \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=moth@magenta.com \
--cc=piggin@cyberone.com.au \
/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).