From: Anuj Gupta <anuj1072538@gmail.com>
To: axboe@kernel.dk, asml.silence@gmail.com, kbusch@kernel.org,
hch@lst.de, sagi@grimberg.me,
James.Bottomley@HansenPartnership.com, mkp@kernel.org,
bernd@bsbernd.com, joannelkoong@gmail.com, miklos@szeredi.hu
Cc: io-uring@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
fuse-devel@lists.linux.dev, joshi.k@samsung.com,
anuj20.g@samsung.com
Subject: [PATCH v3 0/5] dma-buf backed NVMe passthrough I/O
Date: Fri, 30 Oct 2026 07:15:35 +0530 [thread overview]
Message-ID: <20261030014540.3065403-1-anuj1072538@gmail.com> (raw)
This series adds support for dma-buf registered buffers in NVMe
uring_cmd passthrough.
Patches 1-2 add import flags to the fixed buffer import helpers, so
uring_cmd users have to opt in to dma-buf. Patch 3 adds the io_uring
side, patch 4 lets the block layer map dma-buf iterators for
passthrough, and patch 5 enables it for the NVMe namespace character
device.
Tested with this liburing test:
https://github.com/anuj7781/liburing/tree/rw-dmabuf-pt
Changes since v2:
- return -EOPNOTSUPP when the controller has no dma-buf support (Pavel)
v2: https://lore.kernel.org/linux-block/20261022144501.2478417-1-anuj1072538@gmail.com/
Changes since v1:
- split into io_uring, block and nvme patches (Christoph)
- pass import flags to io_import_reg_buf() and
io_uring_cmd_import_fixed(), and make callers opt in to dma-buf
(Christoph, Pavel)
- add io_uring_cmd_hw_done(), so nvme no longer handles the dma-buf
map (Pavel)
- warn if task_work is queued with a dma-buf map attached (Pavel)
- make the -EREMOTEIO conversion explicit and comment it (Christoph)
- refuse dma-bufs larger than 4GiB on the character device
v1: https://lore.kernel.org/linux-nvme/20261016103453.1129150-1-anuj1072538@gmail.com/
Anuj Gupta (5):
io_uring/rsrc: pass import flags to io_import_reg_buf()
io_uring/uring_cmd: add import flags to io_uring_cmd_import_fixed()
io_uring/uring_cmd: support dma-buf registered buffers
block: map dma-buf iterators in blk_rq_map_user_iov()
nvme: support dma-buf registered buffers for passthrough
block/blk-map.c | 15 ++++++++++++++-
drivers/nvme/host/core.c | 16 ++++++++++++++++
drivers/nvme/host/ioctl.c | 5 +++--
drivers/scsi/scsi_bsg.c | 2 +-
fs/fuse/dev_uring.c | 2 +-
include/linux/io_uring/cmd.h | 14 ++++++++++++--
io_uring/net.c | 6 +++---
io_uring/rsrc.c | 6 +++---
io_uring/rsrc.h | 13 +++----------
io_uring/rw.c | 5 +++--
io_uring/uring_cmd.c | 31 +++++++++++++++++++++++++++++--
11 files changed, 88 insertions(+), 27 deletions(-)
base-commit: 70866cfa169d5ee149364267289e71d50f9a7ae9
--
2.43.0
next reply other threads:[~2026-10-30 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 1:45 Anuj Gupta [this message]
2026-10-30 1:45 ` [PATCH v3 1/5] io_uring/rsrc: pass import flags to io_import_reg_buf() Anuj Gupta
2026-10-30 1:45 ` [PATCH v3 2/5] io_uring/uring_cmd: add import flags to io_uring_cmd_import_fixed() Anuj Gupta
2026-10-30 1:45 ` [PATCH v3 3/5] io_uring/uring_cmd: support dma-buf registered buffers Anuj Gupta
2026-10-30 1:45 ` [PATCH v3 4/5] block: map dma-buf iterators in blk_rq_map_user_iov() Anuj Gupta
2026-10-30 1:45 ` [PATCH v3 5/5] nvme: support dma-buf registered buffers for passthrough Anuj Gupta
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=20261030014540.3065403-1-anuj1072538@gmail.com \
--to=anuj1072538@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bernd@bsbernd.com \
--cc=fuse-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=joannelkoong@gmail.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mkp@kernel.org \
--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