From: Sidong Yang <[email protected]>
To: Josef Bacik <[email protected]>,
David Sterba <[email protected]>, Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected],
[email protected], Sidong Yang <[email protected]>
Subject: [RFC PATCH v4 0/5] introduce io_uring_cmd_import_fixed_vec
Date: Mon, 17 Mar 2025 13:57:37 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
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
Additionally, There is a commit that fixed a memory bug in btrfs uring encoded
read.
v2:
- don't export iou_vc, use bvec for btrfs
- use io_is_compat for checking compat
- reduce allocation/free for import fixed vec
v3:
- add iou_vec cache in io_uring_cmd and use it
- also encoded write fixed supported
v4:
- add a patch that introduce io_async_cmd
- add a patch that fixes a bug in btrfs encoded read
Sidong Yang (5):
io_uring/cmd: introduce io_async_cmd for hide io_uring_cmd_data
io-uring/cmd: add iou_vec field for io_uring_cmd
io-uring/cmd: introduce io_uring_cmd_import_fixed_vec
btrfs: ioctl: introduce btrfs_uring_import_iovec()
btrfs: ioctl: don't free iov when -EAGAIN in uring encoded read
fs/btrfs/ioctl.c | 35 ++++++++++++++++-----
include/linux/io_uring/cmd.h | 14 +++++++++
io_uring/io_uring.c | 4 +--
io_uring/opdef.c | 3 +-
io_uring/uring_cmd.c | 60 +++++++++++++++++++++++++++++++-----
io_uring/uring_cmd.h | 10 ++++++
6 files changed, 108 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2025-03-17 13:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 13:57 Sidong Yang [this message]
2025-03-17 13:57 ` [RFC PATCH v4 1/5] io_uring/cmd: introduce io_async_cmd for hide io_uring_cmd_data Sidong Yang
2025-03-17 13:57 ` [RFC PATCH v4 2/5] io-uring/cmd: add iou_vec field for io_uring_cmd Sidong Yang
2025-03-17 13:57 ` [RFC PATCH v4 3/5] io-uring/cmd: introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-17 13:57 ` [RFC PATCH v4 4/5] btrfs: ioctl: introduce btrfs_uring_import_iovec() Sidong Yang
2025-03-17 15:37 ` Caleb Sander Mateos
2025-03-18 0:51 ` Sidong Yang
2025-03-17 15:40 ` Jens Axboe
2025-03-18 1:58 ` Sidong Yang
2025-03-18 7:25 ` Pavel Begunkov
2025-03-18 7:55 ` Sidong Yang
2025-03-18 13:18 ` Jens Axboe
2025-03-17 13:57 ` [RFC PATCH v4 5/5] btrfs: ioctl: don't free iov when -EAGAIN in uring encoded read Sidong Yang
2025-03-18 7:21 ` Pavel Begunkov
2025-03-18 7:58 ` Sidong Yang
2025-03-18 7:30 ` [RFC PATCH v4 0/5] introduce io_uring_cmd_import_fixed_vec Pavel Begunkov
2025-03-18 7:41 ` Sidong Yang
2025-03-18 13:19 ` 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] \
[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