From: Leon Romanovsky <leon@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Jason Gunthorpe <jgg@nvidia.com>, Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: [PATCH 0/4] Properly take MMIO path
Date: Mon, 13 Oct 2025 18:34:08 +0300 [thread overview]
Message-ID: <cover.1760369219.git.leon@kernel.org> (raw)
This is NVMe and block specific patches from my DMA series [1] which
improved DMA physical API to properly support MMIO memory.
Thanks
[1] https://lore.kernel.org/all/cover.1757423202.git.leonro@nvidia.com/
Leon Romanovsky (4):
blk-mq-dma: migrate to dma_map_phys instead of map_page
blk-mq-dma: unify DMA unmap routine
block-dma: properly take MMIO path
nvme-pci: unmap MMIO pages with appropriate interface
block/blk-mq-dma.c | 52 +++++++++++++++++++++++++++++++++--
drivers/nvme/host/pci.c | 18 ++++++++----
include/linux/bio-integrity.h | 1 +
include/linux/blk-integrity.h | 3 +-
include/linux/blk-mq-dma.h | 35 ++---------------------
include/linux/blk_types.h | 2 ++
6 files changed, 68 insertions(+), 43 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-13 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 15:34 Leon Romanovsky [this message]
2025-10-13 15:34 ` [PATCH 1/4] blk-mq-dma: migrate to dma_map_phys instead of map_page Leon Romanovsky
2025-10-15 4:16 ` Christoph Hellwig
2025-10-13 15:34 ` [PATCH 2/4] blk-mq-dma: unify DMA unmap routine Leon Romanovsky
2025-10-13 18:53 ` Keith Busch
2025-10-13 19:35 ` Leon Romanovsky
2025-10-13 15:34 ` [PATCH 3/4] block-dma: properly take MMIO path Leon Romanovsky
2025-10-13 19:01 ` Keith Busch
2025-10-13 19:29 ` Leon Romanovsky
2025-10-13 19:34 ` Keith Busch
2025-10-15 4:18 ` Christoph Hellwig
2025-10-13 15:34 ` [PATCH 4/4] nvme-pci: unmap MMIO pages with appropriate interface Leon Romanovsky
2025-10-15 4:20 ` Christoph Hellwig
2025-10-15 6:44 ` Leon Romanovsky
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=cover.1760369219.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=sagi@grimberg.me \
/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