From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs: raid56: part 1, refactor/cleanup
Date: Mon, 10 Oct 2022 18:36:05 +0800 [thread overview]
Message-ID: <cover.1665397731.git.wqu@suse.com> (raw)
This is the cleanup/refactor part for the incoming RAID56 feature, which
will do data checksum verification during RMW cycle to address
destructive RMW.
The important parts of the cleanup are:
- Make pointer members of btrfs_raid_bio to be allocated separately
This will make later expanding (csum_buf and csum_bitmap) easier.
- Make it explicit that all cached rbio should have all its data sectors
uptodate
This means, if we steal one rbio, all the data sectors should be
uptodate.
Qu Wenruo (5):
btrfs: raid56: properly handle the error when unable to find the
missing stripe
btrfs: raid56: avoid double freeing for rbio if full_stripe_write()
failed
btrfs: raid56: cleanup for function __free_raid_bio()
btrfs: raid56: allocate memory separately for rbio pointers
btrfs: raid56: make it more explicit that cache rbio should have all
its data sectors uptodate
fs/btrfs/raid56.c | 189 +++++++++++++++++++++++++++-------------------
1 file changed, 113 insertions(+), 76 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-10 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 10:36 Qu Wenruo [this message]
2022-10-10 10:36 ` [PATCH 1/5] btrfs: raid56: properly handle the error when unable to find the missing stripe Qu Wenruo
2022-10-10 10:36 ` [PATCH 2/5] btrfs: raid56: avoid double freeing for rbio if full_stripe_write() failed Qu Wenruo
2022-10-10 10:36 ` [PATCH 3/5] btrfs: raid56: cleanup for function __free_raid_bio() Qu Wenruo
2022-10-10 10:36 ` [PATCH 4/5] btrfs: raid56: allocate memory separately for rbio pointers Qu Wenruo
2022-10-10 10:36 ` [PATCH 5/5] btrfs: raid56: make it more explicit that cache rbio should have all its data sectors uptodate Qu Wenruo
2022-10-10 17:35 ` [PATCH 0/5] btrfs: raid56: part 1, refactor/cleanup David Sterba
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=cover.1665397731.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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