All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: war <war@starband.net>
Cc: Jens Axboe <axboe@suse.de>,
	Marvin Justice <mjustice@austin.rr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: highmem question
Date: Fri, 07 Dec 2001 19:46:51 -0800	[thread overview]
Message-ID: <3C118D2B.9050807@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0112071404280.29154-100000@mustard.heime.net> <01120719534703.00764@bozo> <20011208015446.GC32569@suse.de> <01120720102404.00764@bozo> <20011208021040.GE32569@suse.de> <3C118C6B.33EA558F@starband.net>

war wrote:

> I have 1GB of ram + HIGHMEM support on.
> 
> How much of a performance impact are we talking about?
> 
> 896MB of ram would be ok if HIGHMEM impacted the machine severely.
> 
> Has anyone done any benchmarks with HIGHMEM vs NO HIGHMEM?
> 


1 GB is really the worst case.  You don't gain too much memory this way, 
and suffer the necessary slowdown.

Personally I would support dropping the kernel boundary to 0xb8000000 
and use 0xb8000000-0xbfffffff for iomem; that way 1 GB wouldn't need 
HIGHMEM.

	-hpa



      reply	other threads:[~2001-12-08  3:47 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
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 [this message]

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=3C118D2B.9050807@zytor.com \
    --to=hpa@zytor.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjustice@austin.rr.com \
    --cc=war@starband.net \
    /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.