From: David Sterba <dsterba@suse.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Pavel Begunkov <asml.silence@gmail.com>,
Sidong Yang <sidong.yang@furiosa.ai>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org
Subject: Re: (subset) [RFC PATCH v5 0/5] introduce io_uring_cmd_import_fixed_vec
Date: Wed, 19 Mar 2025 18:07:10 +0100 [thread overview]
Message-ID: <20250319170710.GK32661@suse.cz> (raw)
In-Reply-To: <f78c156e-8712-4239-b17f-d917be03226a@kernel.dk>
On Wed, Mar 19, 2025 at 09:27:37AM -0600, 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.
For 6.15 is too late so it makes more sense to take it through the btrfs
patches targetting 6.16.
next prev parent reply other threads:[~2025-03-19 17:07 UTC|newest]
Thread overview: 20+ 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-21 10:28 ` Pavel Begunkov
2025-03-21 11:17 ` Jens Axboe
2025-03-22 15:23 ` 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 [this message]
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-21 9:56 ` Pavel Begunkov
2025-03-20 11:53 ` Pavel Begunkov
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 \
--in-reply-to=20250319170710.GK32661@suse.cz \
--to=dsterba@suse.cz \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dsterba@suse.com \
--cc=io-uring@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sidong.yang@furiosa.ai \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.