public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: mjustice@austin.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: highmem question
Date: Fri, 07 Dec 2001 17:28:38 -0800	[thread overview]
Message-ID: <3C116CC6.2030808@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0112071404280.29154-100000@mustard.heime.net> <9url8t$nmo$1@cesium.transmeta.com> <01120719300102.00764@bozo>

Marvin Justice wrote:

> 
> While it certainly makes sense to expect a performance hit for mem above 4GB 
> on 32 bit systems I don't see why there should be any a priori reason to 
> either move to 64 bit or take a performance hit for if you need, say,  2GB of 
> RAM. The problem is that 2.4 Linux considers HIGHMEM to be anything above 
> 896MB. 
> 


The problem is that in the x86 architecture you don't have any reasonable
way of addressing the physical address space, so you need to map it into
the virtual address space.  You end up with a shortage of virtual address
space.

> 
>>From what I've read it looks like there will be changes in 2.5 to fix all 
> this.
> 


There is no way of fixing it.



  reply	other threads:[~2001-12-08  1:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 13:06 highmem question Roy Sigurd Karlsbakk
2001-12-08  0:01 ` H. Peter Anvin
2001-12-08  1:30   ` Marvin Justice
2001-12-08  1:28     ` H. Peter Anvin [this message]
2001-12-08  1:53       ` Marvin Justice
2001-12-08  1:52         ` H. Peter Anvin
2001-12-08  1:54         ` Jens Axboe
2001-12-08  1:58           ` H. Peter Anvin
2001-12-08  2:02             ` Jens Axboe
2001-12-08  2:10           ` Marvin Justice
2001-12-08  2:08             ` H. Peter Anvin
2001-12-08  2:10             ` Jens Axboe
2001-12-08  3:43               ` war
2001-12-08  3:46                 ` H. Peter Anvin

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=3C116CC6.2030808@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjustice@austin.rr.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