From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <axboe@kernel.dk>, <joshi.k@samsung.com>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCHv4 0/8] blk-mq: introduce blk_map_iter
Date: Thu, 31 Jul 2025 08:05:05 -0700 [thread overview]
Message-ID: <20250731150513.220395-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
Previous version:
https://lore.kernel.org/linux-nvme/20250729143442.2586575-1-kbusch@meta.com/
Changes since v3:
- Fixed special vec handling
- Fixed address check for dma_mapping_error
- Fixed nvme leaks on dma iteration errror
- Added an nvme prep patch to reduce code duplication when unmaping
sgl's
- On the last patch, I retained the previous MPTR setup for when a
single integrity segment exists for non-user requests. A code comment
in the data path claims that is more efficient than the DMA iterator.
Keith Busch (8):
blk-mq-dma: introduce blk_map_iter
blk-mq-dma: provide the bio_vec list being iterated
blk-mq-dma: require unmap caller provide p2p map type
blk-mq: remove REQ_P2PDMA flag
blk-mq-dma: move common dma start code to a helper
blk-mq-dma: add support for mapping integrity metadata
nvme-pci: create common sgl unmapping helper
nvme-pci: convert metadata mapping to dma iter
block/bio.c | 2 +-
block/blk-mq-dma.c | 237 ++++++++++++++++++++--------------
drivers/nvme/host/pci.c | 190 +++++++++++++++------------
include/linux/blk-integrity.h | 17 +++
include/linux/blk-mq-dma.h | 16 ++-
include/linux/blk_types.h | 1 -
6 files changed, 279 insertions(+), 184 deletions(-)
--
2.47.3
next reply other threads:[~2025-07-31 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 15:05 Keith Busch [this message]
2025-07-31 15:05 ` [PATCHv4 1/8] blk-mq-dma: introduce blk_map_iter Keith Busch
2025-07-31 15:05 ` [PATCHv4 2/8] blk-mq-dma: provide the bio_vec list being iterated Keith Busch
2025-07-31 15:05 ` [PATCHv4 3/8] blk-mq-dma: require unmap caller provide p2p map type Keith Busch
2025-07-31 15:05 ` [PATCHv4 4/8] blk-mq: remove REQ_P2PDMA flag Keith Busch
2025-08-08 12:54 ` Kanchan Joshi
2025-07-31 15:05 ` [PATCHv4 5/8] blk-mq-dma: move common dma start code to a helper Keith Busch
2025-07-31 15:05 ` [PATCHv4 6/8] blk-mq-dma: add support for mapping integrity metadata Keith Busch
2025-08-02 23:11 ` kernel test robot
2025-07-31 15:05 ` [PATCHv4 7/8] nvme-pci: create common sgl unmapping helper Keith Busch
2025-07-31 15:05 ` [PATCHv4 8/8] nvme-pci: convert metadata mapping to dma iter Keith Busch
2025-08-08 13:01 ` Kanchan Joshi
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=20250731150513.220395-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.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