From: Raul Miller <moth@magenta.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram.
Date: Thu, 11 Dec 2003 09:41:48 -0500 [thread overview]
Message-ID: <20031211094148.G28449@links.magenta.com> (raw)
In-Reply-To: <20031211054111.GX8039@holomorphy.com>; from wli@holomorphy.com on Wed, Dec 10, 2003 at 09:41:11PM -0800
> On Thu, Dec 11, 2003 at 12:33:39AM -0500, Ed Sweetman wrote:
> > I thought highmem wasn't necesarily needed for memory <=2GB? Highmem
> > incurs some performance hits doesn't it and so the urge to move to it
> > with only 2GB is not very attractive. Anyways i'm just interested in if
> > that's the case or not since 2GB is easy to get to these days and i had
> > heard that highmem could be avoided passed the 1GB barrier.
On Wed, Dec 10, 2003 at 09:41:11PM -0800, William Lee Irwin III 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.
Apologies if I'm asking about the obvious, but...
[1] isn't 0xC0000000 at 3GB?
[2] Even if ELF did restrict a user process to 1GB (which I'm pretty
sure it doesn't), wouldn't the kernel still be able to manage 2GB of
user memory?
Probably my real question is: "what's this about 2:2 split patches"?
Basically, I thought "linux supports 2GB ram" had been been the case
since the dark ages. It's hard for me to comprehend how highmem, or 64
bit cpus, could have much to do with a 1GB limit.
[In my fantasies, I was thinking that the system came up with only 1GB of
the memory easily usable, and that the lack of support for my hardware
meant that it couldn't be properly reconfigured. But I recognize that
I haven't spent the time researching this to see if in fact this is
the case.]
I am in the process of bringing up an cross compilation environment for
amd64 -- I need to do that anyways -- and I'll try building a real 64
bit kernel to see if that helps any. If that doesn't, I guess I'll try
a couple 4G highmem kernels (one 64 bit, one 32 bit). If nothing else,
that will eat up some time...
Thanks,
--
Raul Miller
moth@magenta.com
next prev parent reply other threads:[~2003-12-11 14:41 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:30 ` David Lang
2003-12-11 7:08 ` Martin J. Bligh
2003-12-11 7:19 ` William Lee Irwin III
2003-12-11 7:22 ` Martin J. Bligh
2003-12-11 13:24 ` William Lee Irwin III
2003-12-11 14:41 ` Raul Miller [this message]
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
2003-12-11 6:01 ` PROBLEM: Linux 2.6.0-test11 only lets me use 1GB out of 2GB ram Raul Miller
2003-12-11 6:12 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 4:51 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=20031211094148.G28449@links.magenta.com \
--to=moth@magenta.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