From: Johannes Thumshirn <jth@kernel.org>
To: linux-btrfs@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Filipe Manana <fdmanana@suse.com>,
Naohiro Aota <naohiro.aota@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v4 0/2] implement truncation for RAID stripe-extents
Date: Thu, 17 Oct 2024 11:04:09 +0200 [thread overview]
Message-ID: <20241017090411.25336-1-jth@kernel.org> (raw)
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Implement truncation of RAID stripe-tree entries and add selftests for these
two edge cases of deletion to the RAID stripe-tree selftests.
Changes to v3:
- Use btrfs_duplicate_item() (Filipe)
- User key.offset = 0 in btrfs_search_slot() so we can find "front" delete
Link to v3:
https://lore.kernel.org/linux-btrfs/20241009153032.23336-1-jth@kernel.org
Changes to v2:
- Correctly adjust the btree keys and insert new items instead (Filipe)
- Add selftests
Link to v2:
https://lore.kernel.org/linux-btrfs/20240911095206.31060-1-jth@kernel.org
Johannes Thumshirn (2):
btrfs: implement partial deletion of RAID stripe extents
btrfs: implement self-tests for partial RAID srtipe-tree delete
fs/btrfs/ctree.c | 1 +
fs/btrfs/raid-stripe-tree.c | 78 ++++++++-
fs/btrfs/tests/raid-stripe-tree-tests.c | 214 ++++++++++++++++++++++++
3 files changed, 292 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2024-10-17 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:04 Johannes Thumshirn [this message]
2024-10-17 9:04 ` [PATCH v4 1/2] btrfs: implement partial deletion of RAID stripe extents Johannes Thumshirn
2024-10-22 13:52 ` Filipe Manana
2024-10-22 15:37 ` Johannes Thumshirn
2024-10-22 15:41 ` Filipe Manana
2024-10-17 9:04 ` [PATCH v4 2/2] btrfs: implement self-tests for partial RAID srtipe-tree delete Johannes Thumshirn
2024-10-22 13:57 ` Filipe Manana
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=20241017090411.25336-1-jth@kernel.org \
--to=jth@kernel.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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;
as well as URLs for NNTP newsgroup(s).