From: Pavel Begunkov <[email protected]>
To: Ming Lei <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 0/2] cmd infra for caching iovec/bvec
Date: Sat, 22 Mar 2025 12:09:36 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <Z96F9J5gixbb52E-@fedora>
On 3/22/25 09:42, Ming Lei wrote:
> On Fri, Mar 21, 2025 at 01:13:23PM -0600, Jens Axboe wrote:
>> On 3/21/25 12:04 PM, Pavel Begunkov wrote:
>>> Add infrastructure that is going to be used by commands for importing
>>> vectored registered buffers. It can also be reused later for iovec
>>> caching.
>>>
>>> v2: clear the vec on first ->async_data allocation
>>> fix a memory leak
>>>
>>> Pavel Begunkov (2):
>>> io_uring/cmd: add iovec cache for commands
>>> io_uring/cmd: introduce io_uring_cmd_import_fixed_vec
>>>
>>> include/linux/io_uring/cmd.h | 13 ++++++++++++
>>> io_uring/io_uring.c | 5 +++--
>>> io_uring/opdef.c | 1 +
>>> io_uring/uring_cmd.c | 39 +++++++++++++++++++++++++++++++++++-
>>> io_uring/uring_cmd.h | 11 ++++++++++
>>> 5 files changed, 66 insertions(+), 3 deletions(-)
>>
>> This version works for me - adding in Ming, so he can test and
>> verify as well.
>
> With the two patches, all ublk selftest can run to pass, and kernel doesn't
> panic any more.
thanks for testing.
>
> BTW, I meant vectored fix kernel buffer support for FS read/write, which
> looks not supported yet.
Right, you can't use do a vectored registered buffer read/write/etc.
with a kernel buffer (ala ublk zc provided one). That will likely
need a special version of io_vec_fill_bvec() that would account
for bvec entries not being uniform in size.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-03-22 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 18:04 [PATCH v2 0/2] cmd infra for caching iovec/bvec Pavel Begunkov
2025-03-21 18:04 ` [PATCH v2 1/2] io_uring/cmd: add iovec cache for commands Pavel Begunkov
2025-03-21 18:04 ` [PATCH v2 2/2] io_uring/cmd: introduce io_uring_cmd_import_fixed_vec Pavel Begunkov
2025-03-21 19:13 ` [PATCH v2 0/2] cmd infra for caching iovec/bvec Jens Axboe
2025-03-22 9:42 ` Ming Lei
2025-03-22 12:09 ` Pavel Begunkov [this message]
2025-03-21 19:45 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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