From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, Josef Bacik <[email protected]>,
David Sterba <[email protected]>,
Sidong Yang <[email protected]>
Cc: [email protected], [email protected],
[email protected]
Subject: Re: (subset) [RFC PATCH v5 0/5] introduce io_uring_cmd_import_fixed_vec
Date: Thu, 20 Mar 2025 11:53:33 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/19/25 15:27, Jens Axboe wrote:
> On 3/19/25 9:26 AM, Jens Axboe wrote:
>>
>> On Wed, 19 Mar 2025 06:12:46 +0000, Sidong Yang wrote:
>>> This patche series introduce io_uring_cmd_import_vec. With this function,
>>> Multiple fixed buffer could be used in uring cmd. It's vectored version
>>> for io_uring_cmd_import_fixed(). Also this patch series includes a usage
>>> for new api for encoded read/write in btrfs by using uring cmd.
>>>
>>> There was approximately 10 percent of performance improvements through benchmark.
>>> The benchmark code is in
>>> https://github.com/SidongYang/btrfs-encoded-io-test/blob/main/main.c
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/5] io_uring: rename the data cmd cache
>> commit: 575e7b0629d4bd485517c40ff20676180476f5f9
>> [2/5] io_uring/cmd: don't expose entire cmd async data
>> commit: 5f14404bfa245a156915ee44c827edc56655b067
>> [3/5] io_uring/cmd: add iovec cache for commands
>> commit: fe549edab6c3b7995b58450e31232566b383a249
>> [4/5] io_uring/cmd: introduce io_uring_cmd_import_fixed_vec
>> commit: b24cb04c1e072ecd859a98b2e4258ca8fe8d2d4d
>
> 1-4 look pretty straight forward to me - I'll be happy to queue the
> btrfs one as well if the btrfs people are happy with it, just didn't
> want to assume anything here.
fwiw, finally got time to wire a hacky test with a separate cmd,
works fine, but I'll need to setup btrfs to test the last patch.
--
Pavel Begunkov
prev parent reply other threads:[~2025-03-20 11:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 6:12 [RFC PATCH v5 0/5] introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-19 6:12 ` [RFC PATCH v5 1/5] io_uring: rename the data cmd cache Sidong Yang
2025-03-19 6:12 ` [RFC PATCH v5 2/5] io_uring/cmd: don't expose entire cmd async data Sidong Yang
2025-03-19 6:12 ` [RFC PATCH v5 3/5] io_uring/cmd: add iovec cache for commands Sidong Yang
2025-03-19 6:12 ` [RFC PATCH v5 4/5] io_uring/cmd: introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-19 6:12 ` [RFC PATCH v5 5/5] btrfs: ioctl: introduce btrfs_uring_import_iovec() Sidong Yang
2025-03-20 12:01 ` Pavel Begunkov
2025-03-20 16:19 ` Sidong Yang
2025-03-19 15:26 ` (subset) [RFC PATCH v5 0/5] introduce io_uring_cmd_import_fixed_vec Jens Axboe
2025-03-19 15:27 ` Jens Axboe
2025-03-19 17:07 ` David Sterba
2025-03-19 17:10 ` Jens Axboe
2025-03-20 1:47 ` Sidong Yang
2025-03-20 12:04 ` Pavel Begunkov
2025-03-20 16:10 ` Sidong Yang
2025-03-20 11:53 ` Pavel Begunkov [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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