From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Cc: linux-fsdevel@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
David Wei <dw@davidwei.uk>,
Vishal Verma <vishal1.verma@intel.com>,
asml.silence@gmail.com
Subject: [RFC 08/12] io_uring: add basic dmabuf helpers
Date: Fri, 27 Jun 2025 16:10:35 +0100 [thread overview]
Message-ID: <a4307ea944f7c8453165c02cb05839674f150b5f.1751035820.git.asml.silence@gmail.com> (raw)
In-Reply-To: <cover.1751035820.git.asml.silence@gmail.com>
Add basic dmabuf helpers and structures for io_uring, which will be used
for dmabuf buffer registration. That can also be reused in other places
in io_uring, which is ommited from the series.
Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
---
io_uring/Makefile | 1 +
io_uring/dmabuf.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++
io_uring/dmabuf.h | 34 +++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
create mode 100644 io_uring/dmabuf.c
create mode 100644 io_uring/dmabuf.h
diff --git a/io_uring/Makefile b/io_uring/Makefile
index d97c6b51d584..0f5a7ec38452 100644
--- a/io_uring/Makefile
+++ b/io_uring/Makefile
@@ -21,3 +21,4 @@ obj-$(CONFIG_EPOLL) += epoll.o
obj-$(CONFIG_NET_RX_BUSY_POLL) += napi.o
obj-$(CONFIG_NET) += net.o cmd_net.o
obj-$(CONFIG_PROC_FS) += fdinfo.o
+obj-$(CONFIG_DMA_SHARED_BUFFER) += dmabuf.o
diff --git a/io_uring/dmabuf.c b/io_uring/dmabuf.c
new file mode 100644
index 000000000000..cb9d8bb5d5b3
--- /dev/null
+++ b/io_uring/dmabuf.c
@@ -0,0 +1,60 @@
+#include "dmabuf.h"
+
+void io_dmabuf_release(struct io_dmabuf *buf)
+{
+ if (buf->sgt)
+ dma_buf_unmap_attachment_unlocked(buf->attach, buf->sgt,
+ buf->dir);
+ if (buf->attach)
+ dma_buf_detach(buf->dmabuf, buf->attach);
+ if (buf->dmabuf)
+ dma_buf_put(buf->dmabuf);
+ if (buf->dev)
+ put_device(buf->dev);
+
+ memset(buf, 0, sizeof(*buf));
+}
+
+int io_dmabuf_import(struct io_dmabuf *buf, int dmabuf_fd,
+ struct device *dev, enum dma_data_direction dir)
+{
+ unsigned long total_size = 0;
+ struct scatterlist *sg;
+ int i, ret;
+
+ if (WARN_ON_ONCE(!dev))
+ return -EFAULT;
+
+ buf->dir = dir;
+ buf->dmabuf = dma_buf_get(dmabuf_fd);
+ if (IS_ERR(buf->dmabuf)) {
+ ret = PTR_ERR(buf->dmabuf);
+ buf->dmabuf = NULL;
+ goto err;
+ }
+
+ buf->attach = dma_buf_attach(buf->dmabuf, dev);
+ if (IS_ERR(buf->attach)) {
+ ret = PTR_ERR(buf->attach);
+ buf->attach = NULL;
+ goto err;
+ }
+
+ buf->sgt = dma_buf_map_attachment_unlocked(buf->attach, dir);
+ if (IS_ERR(buf->sgt)) {
+ ret = PTR_ERR(buf->sgt);
+ buf->sgt = NULL;
+ goto err;
+ }
+
+ for_each_sgtable_dma_sg(buf->sgt, sg, i)
+ total_size += sg_dma_len(sg);
+
+ buf->dir = dir;
+ buf->dev = get_device(dev);
+ buf->len = total_size;
+ return 0;
+err:
+ io_dmabuf_release(buf);
+ return ret;
+}
diff --git a/io_uring/dmabuf.h b/io_uring/dmabuf.h
new file mode 100644
index 000000000000..c785ccfe0b9e
--- /dev/null
+++ b/io_uring/dmabuf.h
@@ -0,0 +1,34 @@
+// SPDX-License-Identifier: GPL-2.0
+#ifndef IOU_DMABUF_H
+#define IOU_DMABUF_H
+
+#include <linux/io_uring_types.h>
+#include <linux/dma-buf.h>
+
+struct io_dmabuf {
+ size_t len;
+ struct dma_buf_attachment *attach;
+ struct dma_buf *dmabuf;
+ struct sg_table *sgt;
+ struct device *dev;
+ enum dma_data_direction dir;
+};
+
+#ifdef CONFIG_DMA_SHARED_BUFFER
+void io_dmabuf_release(struct io_dmabuf *buf);
+int io_dmabuf_import(struct io_dmabuf *buf, int dmabuf_fd,
+ struct device *dev, enum dma_data_direction dir);
+
+#else
+static inline void io_dmabuf_release(struct io_dmabuf *buf)
+{
+}
+
+static inline int io_dmabuf_import(struct io_dmabuf *buf, int dmabuf_fd,
+ struct device *dev, enum dma_data_direction dir)
+{
+ return -EOPNOTSUPP;
+}
+#endif
+
+#endif
--
2.49.0
next prev parent reply other threads:[~2025-06-27 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 15:10 [RFC 00/12] io_uring dmabuf read/write support Pavel Begunkov
2025-06-27 15:10 ` [RFC 01/12] file: add callback returning dev for dma operations Pavel Begunkov
2025-06-27 15:10 ` [RFC 02/12] iov_iter: introduce iter type for pre-registered dma Pavel Begunkov
2025-06-27 15:10 ` [RFC 03/12] block: move around bio flagging helpers Pavel Begunkov
2025-06-27 15:10 ` [RFC 04/12] block: introduce dmavec bio type Pavel Begunkov
2025-06-27 15:10 ` [RFC 05/12] block: implement ->get_dma_device callback Pavel Begunkov
2025-06-27 15:10 ` [RFC 06/12] nvme-pci: add support for user passed dma vectors Pavel Begunkov
2025-06-27 15:10 ` [RFC 07/12] io_uring/rsrc: extended reg buffer registration Pavel Begunkov
2025-06-27 15:10 ` Pavel Begunkov [this message]
2025-06-27 15:10 ` [RFC 09/12] io_uring/rsrc: add imu flags Pavel Begunkov
2025-06-27 15:10 ` [RFC 10/12] io_uring/rsrc: add dmabuf-backed buffer registeration Pavel Begunkov
2025-06-27 15:10 ` [RFC 11/12] io_uring/rsrc: implement dmabuf regbuf import Pavel Begunkov
2025-06-27 15:10 ` [RFC 12/12] io_uring/rw: enable dma registered buffers Pavel Begunkov
2025-07-03 14:23 ` [RFC 00/12] io_uring dmabuf read/write support Christoph Hellwig
2025-07-03 14:37 ` Christian König
2025-07-07 11:15 ` Pavel Begunkov
2025-07-07 14:48 ` Christoph Hellwig
2025-07-07 15:41 ` Pavel Begunkov
2025-07-08 9:45 ` Christoph Hellwig
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=a4307ea944f7c8453165c02cb05839674f150b5f.1751035820.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=vishal1.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox