From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>,
Khalid Aziz <khalid@gonehiking.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Hannes Reinecke <hare@suse.com>,
Ondrej Zary <linux@rainbow-software.org>
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: start removing block bounce buffering support v2
Date: Fri, 26 Mar 2021 17:15:31 -0600 [thread overview]
Message-ID: <5dad4408-7539-6edd-7aa8-6ddf9af38c9e@kernel.dk> (raw)
In-Reply-To: <20210326055822.1437471-1-hch@lst.de>
On 3/25/21 11:58 PM, Christoph Hellwig wrote:
> Hi all,
>
> this series starts to clean up and remove the impact of the legacy old
> block layer bounce buffering code.
>
> First it removes support for ISA bouncing. This was used by three SCSI
> drivers. One of them actually had an active user and developer 5 years
> ago so I've converted it to use a local bounce buffer - Ondrej, can you
> test the coversion? The next one has been known broken for years, and
> the third one looks like it has no users for the ISA support so they
> are just dropped.
>
> It then removes support for dealing with bounce buffering highmem pages
> for passthrough requests as we can just use the copy instead of the map
> path for them. This will reduce efficiency for such setups on highmem
> systems (e.g. usb-storage attached DVD drives), but then again that is
> what you get for using a driver not using modern interfaces on a 32-bit
> highmem system. It does allow to streamline the common path pretty nicely.
The core parts look good to me. If we can get the SCSI side to sign off
on those changes, I can take it for 5.13.
--
Jens Axboe
next prev parent reply other threads:[~2021-03-26 23:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 5:58 start removing block bounce buffering support v2 Christoph Hellwig
2021-03-26 5:58 ` [PATCH 1/8] aha1542: use a local bounce buffer Christoph Hellwig
2021-03-29 6:22 ` Hannes Reinecke
2021-03-26 5:58 ` [PATCH 2/8] Buslogic: remove ISA support Christoph Hellwig
2021-03-29 6:22 ` Hannes Reinecke
2021-03-29 20:29 ` Khalid Aziz
2021-03-30 17:03 ` Christoph Hellwig
2021-03-30 17:15 ` Khalid Aziz
2021-03-30 17:31 ` Christoph Hellwig
2021-03-26 5:58 ` [PATCH 3/8] BusLogic: reject broken old firmware that requires ISA-style bounce buffering Christoph Hellwig
2021-03-29 6:23 ` Hannes Reinecke
2021-03-29 20:33 ` Khalid Aziz
2021-03-26 5:58 ` [PATCH 4/8] advansys: remove ISA support Christoph Hellwig
2021-03-29 6:31 ` Hannes Reinecke
2021-03-30 17:26 ` Christoph Hellwig
2021-03-26 5:58 ` [PATCH 5/8] scsi: remove the unchecked_isa_dma flag Christoph Hellwig
2021-03-29 6:31 ` Hannes Reinecke
2021-03-26 5:58 ` [PATCH 6/8] block: remove BLK_BOUNCE_ISA support Christoph Hellwig
2021-03-29 6:32 ` Hannes Reinecke
2021-03-26 5:58 ` [PATCH 7/8] block: refactor the bounce buffering code Christoph Hellwig
2021-03-29 6:34 ` Hannes Reinecke
2021-03-26 5:58 ` [PATCH 8/8] block: stop calling blk_queue_bounce for passthrough requests Christoph Hellwig
2021-03-29 6:37 ` Hannes Reinecke
2021-03-26 23:15 ` Jens Axboe [this message]
2021-03-30 3:08 ` start removing block bounce buffering support v2 Martin K. Petersen
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=5dad4408-7539-6edd-7aa8-6ddf9af38c9e@kernel.dk \
--to=axboe@kernel.dk \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=khalid@gonehiking.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=martin.petersen@oracle.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).