public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Sidong Yang <[email protected]>,
	Josef Bacik <[email protected]>,
	David Sterba <[email protected]>, Jens Axboe <[email protected]>,
	Mark Harmstone <[email protected]>
Cc: [email protected], [email protected],
	[email protected]
Subject: Re: [RFC PATCH v3 0/3] introduce io_uring_cmd_import_fixed_vec
Date: Sun, 16 Mar 2025 07:22:08 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 3/15/25 17:23, 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
> 
> ./main -l
> Elapsed time: 0.598997 seconds
> ./main -l -f
> Elapsed time: 0.540332 seconds

It's probably precise, but it's usually hard to judge about
performance from such short runs. Mark, do we have some benchmark
for the io_uring cmd?

-- 
Pavel Begunkov


      parent reply	other threads:[~2025-03-16  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 17:23 [RFC PATCH v3 0/3] introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-15 17:23 ` [RFC PATCH v3 1/3] io-uring/cmd: add iou_vec field for io_uring_cmd Sidong Yang
2025-03-16  7:24   ` Pavel Begunkov
2025-03-16  8:02     ` Sidong Yang
2025-03-16  8:49       ` Sidong Yang
2025-03-15 17:23 ` [RFC PATCH v3 2/3] io-uring/cmd: introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-15 17:23 ` [RFC PATCH v3 3/3] btrfs: ioctl: introduce btrfs_uring_import_iovec() Sidong Yang
2025-03-16  7:22 ` 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] \
    [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