public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Joanne Koong <joannelkoong@gmail.com>
To: axboe@kernel.dk, io-uring@vger.kernel.org
Cc: csander@purestorage.com, bernd@bsbernd.com, hch@infradead.org,
	asml.silence@gmail.com
Subject: [PATCH v2 5/9] io_uring/kbuf: return buffer id in buffer selection
Date: Tue, 17 Feb 2026 18:52:03 -0800	[thread overview]
Message-ID: <20260218025207.1425553-6-joannelkoong@gmail.com> (raw)
In-Reply-To: <20260218025207.1425553-1-joannelkoong@gmail.com>

Return the id of the selected buffer in io_buffer_select(). This is
needed for kernel-managed buffer rings to later recycle the selected
buffer.

Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
 include/linux/io_uring/cmd.h   | 2 +-
 include/linux/io_uring_types.h | 2 ++
 io_uring/kbuf.c                | 7 +++++--
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/include/linux/io_uring/cmd.h b/include/linux/io_uring/cmd.h
index bd681d8ab1d4..31f47cce99f5 100644
--- a/include/linux/io_uring/cmd.h
+++ b/include/linux/io_uring/cmd.h
@@ -71,7 +71,7 @@ void io_uring_cmd_issue_blocking(struct io_uring_cmd *ioucmd);
 
 /*
  * Select a buffer from the provided buffer group for multishot uring_cmd.
- * Returns the selected buffer address and size.
+ * Returns the selected buffer address, size, and id.
  */
 struct io_br_sel io_uring_cmd_buffer_select(struct io_uring_cmd *ioucmd,
 					    unsigned buf_group, size_t *len,
diff --git a/include/linux/io_uring_types.h b/include/linux/io_uring_types.h
index 36cc2e0346d9..5a56bb341337 100644
--- a/include/linux/io_uring_types.h
+++ b/include/linux/io_uring_types.h
@@ -100,6 +100,8 @@ struct io_br_sel {
 		void *kaddr;
 	};
 	ssize_t val;
+	/* id of the selected buffer */
+	unsigned buf_id;
 };
 
 
diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
index 1d86ad7803fd..d20221f1b9b2 100644
--- a/io_uring/kbuf.c
+++ b/io_uring/kbuf.c
@@ -206,6 +206,7 @@ static struct io_br_sel io_ring_buffer_select(struct io_kiocb *req, size_t *len,
 	req->flags |= REQ_F_BUFFER_RING | REQ_F_BUFFERS_COMMIT;
 	req->buf_index = READ_ONCE(buf->bid);
 	sel.buf_list = bl;
+	sel.buf_id = req->buf_index;
 	if (bl->flags & IOBL_KERNEL_MANAGED)
 		sel.kaddr = (void *)(uintptr_t)READ_ONCE(buf->addr);
 	else
@@ -229,10 +230,12 @@ struct io_br_sel io_buffer_select(struct io_kiocb *req, size_t *len,
 
 	bl = io_buffer_get_list(ctx, buf_group);
 	if (likely(bl)) {
-		if (bl->flags & IOBL_BUF_RING)
+		if (bl->flags & IOBL_BUF_RING) {
 			sel = io_ring_buffer_select(req, len, bl, issue_flags);
-		else
+		} else {
 			sel.addr = io_provided_buffer_select(req, len, bl);
+			sel.buf_id = req->buf_index;
+		}
 	}
 	io_ring_submit_unlock(req->ctx, issue_flags);
 	return sel;
-- 
2.47.3


  parent reply	other threads:[~2026-02-18  2:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  2:51 [PATCH v2 0/9] io_uring: add kernel-managed buffer rings Joanne Koong
2026-02-18  2:51 ` [PATCH v2 1/9] io_uring/memmap: chunk allocations in io_region_allocate_pages() Joanne Koong
2026-02-18  2:52 ` [PATCH v2 2/9] io_uring/kbuf: add support for kernel-managed buffer rings Joanne Koong
2026-02-18  2:52 ` [PATCH v2 3/9] io_uring/kbuf: support kernel-managed buffer rings in buffer selection Joanne Koong
2026-02-18  2:52 ` [PATCH v2 4/9] io_uring/kbuf: add buffer ring pinning/unpinning Joanne Koong
2026-02-18  2:52 ` Joanne Koong [this message]
2026-02-18  2:52 ` [PATCH v2 6/9] io_uring/kbuf: add recycling for kernel managed buffer rings Joanne Koong
2026-02-18  2:52 ` [PATCH v2 7/9] io_uring/kbuf: add io_uring_is_kmbuf_ring() Joanne Koong
2026-02-18  2:52 ` [PATCH v2 8/9] io_uring/kbuf: export io_ring_buffer_select() Joanne Koong
2026-02-18  2:52 ` [PATCH v2 9/9] io_uring/cmd: set selected buffer index in __io_uring_cmd_done() Joanne Koong
2026-02-18  8:47 ` [syzbot ci] Re: io_uring: add kernel-managed buffer rings syzbot ci

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=20260218025207.1425553-6-joannelkoong@gmail.com \
    --to=joannelkoong@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bernd@bsbernd.com \
    --cc=csander@purestorage.com \
    --cc=hch@infradead.org \
    --cc=io-uring@vger.kernel.org \
    /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