public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: csander@purestorage.com, io-uring@vger.kernel.org
Subject: Re: [PATCH v5 0/4] io_uring: extend bvec registration
Date: Fri, 3 Apr 2026 10:21:52 -0600	[thread overview]
Message-ID: <789726e1-c896-4073-b712-e4d03cce5133@kernel.dk> (raw)
In-Reply-To: <20260402160929.2749744-1-joannelkoong@gmail.com>

On 4/2/26 10:09 AM, Joanne Koong wrote:
> This series refactors and extends the io_uring registered buffers
> infrastructure to allow external subsystems to register pre-existing bvec
> arrays directly.
> 
> The motivation for the patches in this series is to make fuse zero-copy
> possible. These patches are split out from a previous larger
> fuse-over-io_uring series [1]. The fuse zero-copy work that builds on top of
> this is in [2].
> 
> Thanks,
> Joanne
> 
> [1] https://lore.kernel.org/linux-fsdevel/20260116233044.1532965-1-joannelkoong@gmail.com/
> [2] https://lore.kernel.org/linux-fsdevel/20260324224532.3733468-9-joannelkoong@gmail.com/
> 
> Changelog:
> v4: https://lore.kernel.org/io-uring/20260327172631.3380702-1-joannelkoong@gmail.com/
> v4 -> v5:
> * rebase to origin/for-7.1/io_uring 
> * drop the io_uring_registered_mem_region_get() patch

Series looks good to me, but I don't think you used the right base? It
does not seem to apply to for-7.1/io_uring, patch 1 runs into issues on
the ublk part.

Since this touches both and applies to neither right now, maybe do a
respin and just base it on my for-next. Then I'll setup a
for-7.1/io_uring-fuse branch that is just for-7.1/io_uring and
for-7.1/block merged together.

-- 
Jens Axboe

  parent reply	other threads:[~2026-04-03 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 16:09 [PATCH v5 0/4] io_uring: extend bvec registration Joanne Koong
2026-04-02 16:09 ` [PATCH v5 1/4] io_uring/rsrc: rename io_buffer_register_bvec()/io_buffer_unregister_bvec() Joanne Koong
2026-04-02 16:09 ` [PATCH v5 2/4] io_uring/rsrc: split io_buffer_register_request() logic Joanne Koong
2026-04-02 16:09 ` [PATCH v5 3/4] io_uring/rsrc: add io_buffer_register_bvec() Joanne Koong
2026-04-02 16:09 ` [PATCH v5 4/4] io_uring/rsrc: rename and export IO_IMU_DEST / IO_IMU_SOURCE Joanne Koong
2026-04-03 16:21 ` Jens Axboe [this message]
2026-04-03 17:30   ` [PATCH v5 0/4] io_uring: extend bvec registration Joanne Koong
2026-04-03 18:31     ` Jens Axboe

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=789726e1-c896-4073-b712-e4d03cce5133@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=joannelkoong@gmail.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