public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Allocating more than 890MB in the kernel?
Date: 19 Oct 2001 12:59:20 -0700	[thread overview]
Message-ID: <9qq0mo$eun$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0110191204210.21846-100000@hill.cs.ucr.edu> <3BD08207.7090807@interactivesi.com>

Followup to:  <3BD08207.7090807@interactivesi.com>
By author:    Timur Tabi <ttabi@interactivesi.com>
In newsgroup: linux.dev.kernel
> 
> > Isn't this solved by just recompiling the kernel with HIGHMEM support?
> 
> 
> I don't think so.  The Red Hat 7.1 kernel is compiled with "4GB" support, 
> which apparently is the same as HIGHMEM.  We see the 890MB kernel vmalloc 
> limit still.
> 

That's because you're running out of address space, not memory.
HIGHMEM doesn't do anything for the latter -- it can't.  You start
running into a lot of fundamental problems when your memory size gets
in the same (or higher) ballpark than your address space.

The best solution is go buy a 64-bit CPU.  There isn't much else you
can do about it.

	-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>

  reply	other threads:[~2001-10-19 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 18:48 Allocating more than 890MB in the kernel? Timur Tabi
2001-10-19 19:04 ` John Tyner
2001-10-19 19:41   ` Timur Tabi
2001-10-19 19:59     ` H. Peter Anvin [this message]
2001-10-19 20:21       ` Timur Tabi
2001-10-19 20:32         ` H. Peter Anvin
2001-10-20  4:40         ` Rob Landley
2001-10-20 18:09           ` H. Peter Anvin
2001-10-25  4:04         ` Albert D. Cahalan
2001-10-26 16:13           ` Timur Tabi

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='9qq0mo$eun$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