From: Daniel Vacek <neelx@suse.com>
To: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>
Cc: Daniel Vacek <neelx@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Qu Wenruo <wqu@suse.com>
Subject: [PATCH v2 0/3] btrfs: async checksumming cleanups
Date: Thu, 3 Sep 2026 08:23:13 +0200 [thread overview]
Message-ID: <20260903062317.3928665-1-neelx@suse.com> (raw)
While trying to deal with encryption bounce bios async checksumming,
a solution came up which covers all writes (also the regular !encrypted
ones). As a result the code cleans up quite nicely.
In v2 the first patch was further polished and the new last patch promotes
async checksumming out of EXPERIMENTAL. Qu confirmed it was never meant to
stay there for long.
Details in the patches themselves.
v1: https://lore.kernel.org/linux-btrfs/20260902165137.3781696-1-neelx@suse.com/
Daniel Vacek (3):
btrfs: consume the given iter directly instead of copying in
csum_one_bio()
btrfs: use bio::remaining for async checksumming synchronization
btrfs: promote async checksumming out of EXPERIMENTAL
fs/btrfs/bio.c | 8 --------
fs/btrfs/bio.h | 4 ----
fs/btrfs/file-item.c | 21 +++++++++------------
3 files changed, 9 insertions(+), 24 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-03 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 6:23 Daniel Vacek [this message]
2026-09-03 6:23 ` [PATCH v2 1/3] btrfs: consume the given iter directly instead of copying in csum_one_bio() Daniel Vacek
2026-09-03 6:45 ` Qu Wenruo
2026-09-03 6:23 ` [PATCH v2 2/3] btrfs: use bio::remaining for async checksumming synchronization Daniel Vacek
2026-09-04 22:41 ` Qu Wenruo
2026-09-04 22:50 ` Qu Wenruo
2026-09-03 6:23 ` [PATCH v2 3/3] btrfs: promote async checksumming out of EXPERIMENTAL Daniel Vacek
2026-09-03 6:33 ` Qu Wenruo
2026-09-03 6:41 ` Daniel Vacek
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=20260903062317.3928665-1-neelx@suse.com \
--to=neelx@suse.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--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
all inboxes | Powered by JetHome®