All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: highmem question
Date: 7 Dec 2001 16:01:33 -0800	[thread overview]
Message-ID: <9url8t$nmo$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0112071404280.29154-100000@mustard.heime.net>

Followup to:  <Pine.LNX.4.30.0112071404280.29154-100000@mustard.heime.net>
By author:    Roy Sigurd Karlsbakk <roy@karlsbakk.net>
In newsgroup: linux.dev.kernel
> 
> I heard that himem slows down systems.

It does, because it's a hack to extend 32-bit machines beyond their
architectural lifetime.

> - How much memory can Linux use without highmem enabled? (I've heard it's
>   1GB, but Linux found 1,2GB without ...)

On i386, it supports 896 MB without HIGHMEM.

> - How much is a system slowed down?

Depends completely on your application mix and amount of RAM -- and
whether or not you're using 4G or 64G HIGHMEM, the latter being more
severe across a whole bunch of axes.

> - How can this be fixed? I've heard it's a PCI issue (stuff being memory
>   mapped above the 2GB limit?)

Go to a 64-bit CPU architecture.

	-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-12-08  0:02 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 [this message]
2001-12-08  1:30   ` Marvin Justice
2001-12-08  1:28     ` H. Peter Anvin
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='9url8t$nmo$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.