From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
Ming Lei <ming.lei@redhat.com>
Cc: Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH 0/4] io_uring: support vectored fixed kernel buffer
Date: Wed, 02 Apr 2025 07:12:46 -0600 [thread overview]
Message-ID: <174359956673.20480.12310459002400756833.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250325135155.935398-1-ming.lei@redhat.com>
On Tue, 25 Mar 2025 21:51:49 +0800, Ming Lei wrote:
> This patchset supports vectored fixed buffer for kernel bvec buffer,
> and use it on for ublk/stripe.
>
> Please review.
>
> Thanks,
> Ming
>
> [...]
Applied, thanks!
[1/4] io_uring: add validate_fixed_range() for validate fixed buffer
(no commit info)
[2/4] block: add for_each_mp_bvec()
(no commit info)
[3/4] io_uring: support vectored kernel fixed buffer
(no commit info)
[4/4] selftests: ublk: enable zero copy for stripe target
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-04-02 13: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
2025-04-02 13:09 ` Jens Axboe
2025-04-02 13:12 ` Jens Axboe [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=174359956673.20480.12310459002400756833.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--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