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: Re: [PATCH v2 0/9] io_uring: add kernel-managed buffer rings
Date: Wed, 18 Feb 2026 13:45:34 -0800 [thread overview]
Message-ID: <CAJnrk1arKMUjZp0128B6WwhJHi-sxkAFfHYgjDeC=vHjgihmBg@mail.gmail.com> (raw)
In-Reply-To: <20260218025207.1425553-1-joannelkoong@gmail.com>
On Tue, Feb 17, 2026 at 6:56 PM Joanne Koong <joannelkoong@gmail.com> wrote:
>
> Currently, io_uring buffer rings require the application to allocate and
> manage the backing buffers. This series introduces buffer rings, where
> the kernel allocates and manages the buffers on behalf of the application.
>
> This is split out from the fuse over io_uring series in [1], which needs the
> kernel to own and manage buffers shared between the fuse server and the
> kernel.
>
> This series is on top of commit 73cf88d775b1f55 in the for-next branch in
> Jens' io-uring tree. The corresponding liburing changes are in [2] and will
> be submitted after the changes in this patchset are accepted.
>
> There was a discussion on v1 about having kernel-managed buffer rings go
> through a user-provided registered memory region. This changes proposed in
> this patchset add a simple straightforward interface where the kernel
> allocates the buffers and the buffers are tied to the lifecycle of the ring,
> which suffices for the majority of use cases. If/when in the future it is
> useful for the buffers to be backed by a prior user registered mem region
> (eg for PMD optimization gains), the changes in this patchset do not preclude
> support for that from being added.
>
> The link to the fuse commits that use the changes in this series is in [3].
>
> Thanks,
> Joanne
I'm going to update v2 with another version, as per the conversation
in this thread [1].
Thanks,
Joanne
[1] https://lore.kernel.org/linux-fsdevel/20260210002852.1394504-1-joannelkoong@gmail.com/T/#t
prev parent reply other threads:[~2026-02-18 21:45 UTC|newest]
Thread overview: 12+ 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 ` [PATCH v2 5/9] io_uring/kbuf: return buffer id in buffer selection Joanne Koong
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
2026-02-18 21:45 ` Joanne Koong [this message]
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='CAJnrk1arKMUjZp0128B6WwhJHi-sxkAFfHYgjDeC=vHjgihmBg@mail.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