From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: Rosen Penev <rosenp@gmail.com>,
linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: raid56: use async_tx API for parity operations
Date: Mon, 29 Jun 2026 05:40:22 -0700 [thread overview]
Message-ID: <akJnttvuvEv55nOh@infradead.org> (raw)
In-Reply-To: <d96ddcc0-a62f-40e4-9f80-34929dc3bcfd@suse.com>
On Mon, Jun 29, 2026 at 02:41:44PM +0930, Qu Wenruo wrote:
> Do you have any benchmark?
Yeah. The async_tx stuff is a mess, and will cause real slow downs
for CPU native operation, while in general offloads have proven to
not be very useful. There might be a tinty use case if your data is
all P2P and never touches the CPU at all, but I don't think btrfs even
supports that right now.
next prev parent reply other threads:[~2026-06-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 2:39 [PATCH] btrfs: raid56: use async_tx API for parity operations Rosen Penev
2026-06-29 5:11 ` Qu Wenruo
2026-06-29 12:40 ` Christoph Hellwig [this message]
2026-06-29 20:01 ` Rosen Penev
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=akJnttvuvEv55nOh@infradead.org \
--to=hch@infradead.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=wqu@suse.com \
/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