public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, Ming Lei <ming.lei@redhat.com>,
	io-uring@vger.kernel.org
Cc: Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH 0/4] io_uring: support vectored fixed kernel buffer
Date: Wed, 2 Apr 2025 13:13:56 +0100	[thread overview]
Message-ID: <26767f79-4ed3-487e-aba8-aa6ff124b2c3@gmail.com> (raw)
In-Reply-To: <c252ec4e-aa97-4831-8062-43fcd1065324@kernel.dk>

On 4/2/25 12:59, Jens Axboe wrote:
> On 4/2/25 1:57 AM, Ming Lei wrote:
>> On Tue, Mar 25, 2025 at 09:51:49PM +0800, Ming Lei wrote:
>>> Hello Jens,
>>>
>>> This patchset supports vectored fixed buffer for kernel bvec buffer,
>>> and use it on for ublk/stripe.
>>>
>>> Please review.
>>>
>>> Thanks,
>>> Ming
>>>
>>>
>>> Ming Lei (4):
>>>    io_uring: add validate_fixed_range() for validate fixed buffer
>>>    block: add for_each_mp_bvec()
>>>    io_uring: support vectored kernel fixed buffer
>>>    selftests: ublk: enable zero copy for stripe target
>>
>> Hello,
>>
>> Ping...
> 
> Looks fine to me and pretty straight forward, but it was in the merge
> window. Anything that makes this important for 6.15? We can still
> include it if so. If not, let's take a look for 6.16 when the merge
> window closes.

fwiw, I looked through it, looks correct, but it'd be a good
to test it aside from ublk. I guess I'll just extend a kernel
hack I used before.

No opinion on 6.15 vs 6.16, but the argument might be to have
it in the same release with ublk zc, and have less probing
for the user.

-- 
Pavel Begunkov


  reply	other threads:[~2025-04-02 12:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 13:51 [PATCH 0/4] io_uring: support vectored fixed kernel buffer Ming Lei
2025-03-25 13:51 ` [PATCH 1/4] io_uring: add validate_fixed_range() for validate fixed buffer Ming Lei
2025-03-25 16:00   ` Caleb Sander Mateos
2025-03-25 13:51 ` [PATCH 2/4] block: add for_each_mp_bvec() Ming Lei
2025-03-25 13:51 ` [PATCH 3/4] io_uring: support vectored kernel fixed buffer Ming Lei
2025-03-25 13:51 ` [PATCH 4/4] selftests: ublk: enable zero copy for stripe target Ming Lei
2025-04-03 22:42   ` Uday Shankar
2025-04-04  0:23     ` Ming Lei
2025-04-02  7:57 ` [PATCH 0/4] io_uring: support vectored fixed kernel buffer Ming Lei
2025-04-02 11:59   ` Jens Axboe
2025-04-02 12:13     ` Pavel Begunkov [this message]
2025-04-02 13:09       ` Jens Axboe
2025-04-02 13:12 ` 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=26767f79-4ed3-487e-aba8-aa6ff124b2c3@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=ming.lei@redhat.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