From: Pavel Begunkov <asml.silence@gmail.com>
To: linux-block@vger.kernel.org, io-uring@vger.kernel.org
Cc: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Philipp Stanner" <phasta@kernel.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org,
"Pavel Begunkov" <asml.silence@gmail.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
"Nitesh Shetty" <nj.shetty@samsung.com>,
"Kanchan Joshi" <joshi.k@samsung.com>,
"Anuj Gupta" <anuj20.g@samsung.com>
Subject: [PATCH 0/5] allow dma-buf-io ctx reuse across files
Date: Wed, 4 Nov 2026 00:18:56 +0000 [thread overview]
Message-ID: <cover.1793751001.git.asml.silence@gmail.com> (raw)
Currently, dma-buf maps can only be used by the file they were
registered with. This means that we can't open a new file, even if it
comes from the same subsystem and point to the same block device and
use it with an old dma-buf registration. That would be too restrictive
for upcoming filsystem support, so lift it now and allow reusing
contexts between files pointing to the same NVMe, even if they refer
to different partitions.
To do that, we add a tag representing for each file, save it from
the file passed during registration and use it to reject files
which tags don't match it. Tags are set by subsystems creating
files, should be unique and represent the instance of the
subsystem.
Pavel Begunkov (5):
dma-buf-io: add tags for sharing ctx b/w files
block: set dma-buf-io tag to block files
io_uring: add data to dma-buf convertion helpers
io_uring/dma-buf: switch to tag file filtering
io_uring/dma-buf: get rid of struct io_buf_dma
block/fops.c | 1 +
drivers/dma-buf/dma-buf-io.c | 3 +++
include/linux/dma-buf-io.h | 22 ++++++++++++++++++++++
include/linux/fs.h | 6 ++++++
io_uring/dma-buf.c | 19 +++++--------------
io_uring/dma-buf.h | 24 ++++++++++++++----------
6 files changed, 51 insertions(+), 24 deletions(-)
--
2.54.0
next reply other threads:[~2026-11-04 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 0:18 Pavel Begunkov [this message]
2026-11-04 0:18 ` [PATCH 1/5] dma-buf-io: add tags for sharing ctx b/w files Pavel Begunkov
2026-11-04 0:18 ` [PATCH 2/5] block: set dma-buf-io tag to block files Pavel Begunkov
2026-11-04 0:18 ` [PATCH 3/5] io_uring: add data to dma-buf convertion helpers Pavel Begunkov
2026-11-04 0:19 ` [PATCH 4/5] io_uring/dma-buf: switch to tag file filtering Pavel Begunkov
2026-11-04 0:19 ` [PATCH 5/5] io_uring/dma-buf: get rid of struct io_buf_dma Pavel Begunkov
2026-11-04 1:07 ` [PATCH 0/5] allow dma-buf-io ctx reuse across files Pavel Begunkov
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.1793751001.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=joshi.k@samsung.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nj.shetty@samsung.com \
--cc=phasta@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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