All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marvin Justice <mjustice@austin.rr.com>
To: Jens Axboe <axboe@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: highmem question
Date: Fri, 7 Dec 2001 20:10:24 -0600	[thread overview]
Message-ID: <01120720102404.00764@bozo> (raw)
In-Reply-To: <Pine.LNX.4.30.0112071404280.29154-100000@mustard.heime.net> <01120719534703.00764@bozo> <20011208015446.GC32569@suse.de>
In-Reply-To: <20011208015446.GC32569@suse.de>


> That's because of highmem page bouncing when doing I/O. There is indeed
> a solution for this -- 2.5 or 2.4 + block-highmem-all patches will
> happily do I/O directly to any page in your system as long as your
> hardware supports it. I'm sure we're beating w2k with that enabled :-)

Will your patch lead to better performance than the CONFIGH_HIGHMEM=n case? 
Unfortunately, W2K with any amount of memory beat Linux with no highmem (see 
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0110.3/0375.html ) so my 
PHB decided to hold off on Linux for now.

Marvin

  parent reply	other threads:[~2001-12-08  2:06 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 [this message]
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=01120720102404.00764@bozo \
    --to=mjustice@austin.rr.com \
    --cc=axboe@suse.de \
    --cc=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.