From: Jens Axboe <axboe@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
arjanv@redhat.com, "David S. Miller" <davem@redhat.com>
Subject: Re: [patch] block highmem zero bounce v14
Date: Mon, 17 Sep 2001 00:00:12 +0200 [thread overview]
Message-ID: <20010917000012.B12270@suse.de> (raw)
In-Reply-To: <20010916234307.A12270@suse.de> <Pine.LNX.4.33.0109161447390.29507-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0109161447390.29507-100000@penguin.transmeta.com>
On Sun, Sep 16 2001, Linus Torvalds wrote:
>
> On Sun, 16 Sep 2001, Jens Axboe wrote:
> >
> > It's against 2.4.10-pre9 and can be found right here:
> >
> > *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.10-pre9/block-highmem-all-14
>
> Jens, what's your feeling about the stability of these things, especially
> wrt weird drivers?
One of the very first decisions I made wrt this patch was to make sure
that weird/old drivers could keep on working exactly the way they do now
and never have to worry about highmem stuff. That basically means
enabling the stuff on a per-driver basis after it's considered safe. The
can_dma_32 for SCSI and highmem for IDE flag serves that purpose. Stand
alone block drivers just use blk_queue_bounce_limit to enable highmem
I/O after blk_init_queue, if they don't they get highmem pages bounced
as they are used too.
That leaves drivers that are 'different', stuff like ide-scsi for
instance. I think I have most of these under control...
> Ie do you think this is really a 2.4.x thing, or early 2.5.x?
Most of it is really a cautious back port of the 2.5 stuff I've been
working on, and with the above considerations it is/was meant as a 2.4
thing :-)
--
Jens Axboe
next prev parent reply other threads:[~2001-09-16 22:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 21:43 [patch] block highmem zero bounce v14 Jens Axboe
2001-09-16 21:48 ` Linus Torvalds
2001-09-16 22:00 ` Jens Axboe [this message]
2001-09-16 23:10 ` Alan Cox
2001-09-16 23:13 ` Jens Axboe
2001-09-21 15:44 ` Arjan van de Ven
2001-09-21 16:13 ` Alan Cox
2001-09-21 16:39 ` spurious interrupt with ac kernel but not with vanilla 2.4.9 Luigi Genoni
2001-09-21 17:03 ` Alan Cox
2001-09-21 17:14 ` Luigi Genoni
2001-09-21 17:28 ` Alan Cox
2001-09-21 17:33 ` Luigi Genoni
2001-09-22 14:39 ` John Levon
2001-09-22 11:00 ` [patch] block highmem zero bounce v14 Jens Axboe
2001-09-22 11:18 ` Arjan van de Ven
2001-09-22 12:11 ` Jens Axboe
2001-09-22 16:32 ` Alan Cox
2001-09-22 16:35 ` Jens Axboe
2001-09-22 16:41 ` Alan Cox
2001-09-22 16:56 ` Jens Axboe
2001-09-22 17:05 ` Arnaldo Carvalho de Melo
2001-09-20 23:43 ` David S. Miller
2001-09-21 5:56 ` Jens Axboe
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=20010917000012.B12270@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.