From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: simplify passthrough bio handling
Date: Sat, 04 Jan 2025 15:27:52 -0700 [thread overview]
Message-ID: <173602967287.135972.1134077263108813311.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250103073417.459715-1-hch@lst.de>
On Fri, 03 Jan 2025 08:33:56 +0100, Christoph Hellwig wrote:
> this series removes the special casing when adding pages to passthrough
> bios in favor of simply checking that they match the queue limits once
> before submissions. This mirrors where the zone append users have been
> moving and a recent doing the same for a single optimizes passthrough
> user.
>
> Diffstat:
> block/bio.c | 107 +-----------------------------
> block/blk-map.c | 128 ++++++++++---------------------------
> block/blk-mq.c | 4 -
> block/blk.h | 8 --
> drivers/nvme/target/passthru.c | 18 +++--
> drivers/nvme/target/zns.c | 3
> drivers/target/target_core_pscsi.c | 6 -
> include/linux/bio.h | 2
> include/linux/blk-mq.h | 8 --
> 9 files changed, 57 insertions(+), 227 deletions(-)
>
> [...]
Applied, thanks!
[1/2] block: remove bio_add_pc_page
commit: 6aeb4f836480617be472de767c4cb09c1060a067
[2/2] block: remove blk_rq_bio_prep
commit: 02ee5d69e3baf2796ba75b928fcbc9cf7884c5e9
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-01-04 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 7:33 simplify passthrough bio handling Christoph Hellwig
2025-01-03 7:33 ` [PATCH 1/2] block: remove bio_add_pc_page Christoph Hellwig
2025-01-04 22:11 ` Sagi Grimberg
2025-02-03 16:49 ` Chaitanya Kulkarni
2025-01-03 7:33 ` [PATCH 2/2] block: remove blk_rq_bio_prep Christoph Hellwig
2025-01-04 22:11 ` Sagi Grimberg
2025-02-03 16:50 ` Chaitanya Kulkarni
2025-01-04 22:27 ` Jens Axboe [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=173602967287.135972.1134077263108813311.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox