From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <axboe@kernel.dk>, <martin.petersen@oracle.com>,
<jgg@nvidia.com>, <leon@kernel.org>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2 0/2] blk-mq-dma: p2p cleanups and integrity fixup
Date: Tue, 2 Sep 2025 13:01:19 -0700 [thread overview]
Message-ID: <20250902200121.3665600-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
This series moves the p2p dma tracking from the caller to the block
layer, and makes it possible to actually use p2p for metadata payloads.
v1:
https://lore.kernel.org/linux-nvme/20250829142307.3769873-1-kbusch@meta.com/
Changes:
Folded in a fixed to patch 1 that was inadvertently included in patch 2.
Added review.
Keith Busch (2):
blk-integrity: enable p2p source and destination
blk-mq-dma: bring back p2p request flags
block/bio-integrity.c | 21 +++++++++++++++++----
block/blk-mq-dma.c | 4 ++++
drivers/nvme/host/pci.c | 21 ++++-----------------
include/linux/bio-integrity.h | 1 +
include/linux/blk-integrity.h | 14 ++++++++++++++
include/linux/blk-mq-dma.h | 11 +++++++++--
include/linux/blk_types.h | 2 ++
7 files changed, 51 insertions(+), 23 deletions(-)
--
2.47.3
next reply other threads:[~2025-09-02 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 20:01 Keith Busch [this message]
2025-09-02 20:01 ` [PATCHv2 1/2] blk-integrity: enable p2p source and destination Keith Busch
2025-09-02 20:01 ` [PATCHv2 2/2] blk-mq-dma: bring back p2p request flags Keith Busch
2025-09-03 6:09 ` Christoph Hellwig
2025-09-03 8:20 ` Leon Romanovsky
2025-09-03 11:02 ` kernel test robot
2025-09-03 7:55 ` [PATCHv2 0/2] blk-mq-dma: p2p cleanups and integrity fixup 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=20250902200121.3665600-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.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.