public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bounce buffer usage
Date: Sun, 23 Dec 2001 15:09:40 +0100	[thread overview]
Message-ID: <20011223150940.E7438@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0112211652430.2896-100000@dragon.pdx.osdl.net>
In-Reply-To: <Pine.LNX.4.33L2.0112211652430.2896-100000@dragon.pdx.osdl.net>

On Fri, Dec 21 2001, Randy.Dunlap wrote:
> Are there any drivers in 2.4.x that support highmem directly,
> or is all of that being done in 2.5.x (BIO patches)?

2.4 + my block-highmem patches support direct highmem I/O.

> Would it be useful to try this with a 2.5.1 kernel?

Sure

-- 
Jens Axboe


  reply	other threads:[~2001-12-23 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22  1:02 bounce buffer usage Randy.Dunlap
2001-12-23 14:09 ` Jens Axboe [this message]
2002-01-08  1:44   ` Randy.Dunlap
2002-01-08  7:42     ` Jens Axboe
2002-01-09 17:23       ` Randy.Dunlap
2002-01-09 18:10         ` Jens Axboe
2002-01-09 22:33         ` Rik van Riel

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=20011223150940.E7438@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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