From: Sidong Yang <[email protected]>
To: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
Josef Bacik <[email protected]>,
David Sterba <[email protected]>
Cc: Sidong Yang <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: [RFC PATCH 0/2] introduce io_uring_cmd_import_fixed_vec
Date: Tue, 11 Mar 2025 11:40:40 +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 in btrfs by using uring cmd.
Sidong Yang (2):
io_uring: cmd: introduce io_uring_cmd_import_fixed_vec
btrfs: ioctl: use registered buffer for IORING_URING_CMD_FIXED
fs/btrfs/ioctl.c | 26 +++++++++++++++++++++-----
include/linux/io_uring/cmd.h | 14 ++++++++++++++
io_uring/uring_cmd.c | 29 +++++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 5 deletions(-)
---
Recently, I've found that io_import_reg_vec() was added for io-uring. I think
it could be used for io-uring cmd. I've tested for btrfs encoded read and it
works. But it seems that there is no performance improvements and I'll keep
find why.
If there is no need to use fixed buffer for btrfs, I think it's good to use
for nvme.
2.43.0
next reply other threads:[~2025-03-11 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 11:40 Sidong Yang [this message]
2025-03-11 11:40 ` [RFC PATCH 1/2] io_uring: cmd: introduce io_uring_cmd_import_fixed_vec Sidong Yang
2025-03-11 13:08 ` Pavel Begunkov
2025-03-12 3:08 ` Sidong Yang
2025-03-11 11:40 ` [RFC PATCH 2/2] btrfs: ioctl: use registered buffer for IORING_URING_CMD_FIXED Sidong Yang
2025-03-11 12:55 ` Pavel Begunkov
2025-03-12 3:05 ` Sidong Yang
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