From: William Lee Irwin III <wli@holomorphy.com>
To: marc.miller@amd.com
Cc: devnull@adc.idt.com, linux-kernel@vger.kernel.org
Subject: Re: >3G Memory support
Date: Wed, 19 Jun 2002 19:08:09 -0700 [thread overview]
Message-ID: <20020620020809.GS22961@holomorphy.com> (raw)
In-Reply-To: <858788618A93D111B45900805F85267A062BB49D@caexmta3.amd.com>
On Wed, Jun 19, 2002 at 07:01:08PM -0700, marc.miller@amd.com wrote:
> Support of 4G of RAM is a configuration option when you compile the
> kernel. Is that setting turned on?
> I think it's in "General Options" when you do a "make menuconfig"
> (I don't have a machine up at the moment that I can check). There
> are three options: Less than 1G, 1G to less than 4G, and 4G or more.
> That last option is the one you would want.
> If that's already enabled, hopefully one of the memory guys can pitch in...
This is actually yet another "32-bit virtualspace sucks" issue. You can't
get at all your RAM from userspace because the virtualspace set aside for
the kernel prevents you from using it to map physical memory. 64-bit
virtualspace is too vast to be easily exhausted this way.
The original form of highmem was "BIGMEM" which used (almost) disjoint
user and kernel virtual address spaces, but this is not terribly
efficient with respect to lazy TLB entry invalidation.
Cheers,
Bill
next prev parent reply other threads:[~2002-06-20 2:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 2:01 >3G Memory support marc.miller
2002-06-20 2:08 ` William Lee Irwin III [this message]
2002-06-20 4:38 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 22:30 devnull
2002-06-20 3:29 ` Brian Gerst
2002-06-20 14:18 ` devnull
2002-06-20 14:42 ` Brian Gerst
2002-06-20 14:50 ` Jirka Kosina
2002-06-20 15:27 ` William Lee Irwin III
2002-06-20 15:42 ` Richard B. Johnson
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=20020620020809.GS22961@holomorphy.com \
--to=wli@holomorphy.com \
--cc=devnull@adc.idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.miller@amd.com \
/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