From: Mark Harmstone <mark@harmstone.com>
To: linux-btrfs@vger.kernel.org
Cc: Mark Harmstone <mark@harmstone.com>
Subject: [PATCH v6 00/16] Remap tree
Date: Fri, 14 Nov 2025 18:47:05 +0000 [thread overview]
Message-ID: <20251114184745.9304-1-mark@harmstone.com> (raw)
This is version 6 of the patch series for the new logical remapping tree
feature - see the previous cover letters for more information including
the rationale:
* RFC: https://lore.kernel.org/all/20250515163641.3449017-1-maharmstone@fb.com/
* Version 1: https://lore.kernel.org/all/20250605162345.2561026-1-maharmstone@fb.com/
* Version 2: https://lore.kernel.org/all/20250813143509.31073-1-mark@harmstone.com/
* Version 3: https://lore.kernel.org/all/20251009112814.13942-1-mark@harmstone.com/
* Version 4: https://lore.kernel.org/all/20251024181227.32228-1-mark@harmstone.com/
* Version 5: https://lore.kernel.org/all/20251110171511.20900-1-mark@harmstone.com/
Changes since version 5:
* Fixed locking in btrfs_handle_fully_remapped_bgs()
* btrfs_mark_bg_fully_remapped() now puts BGs straight onto discard list if
using async discard, rather than fully_remapped_bgs
* Now using btrfs_mark_bg_unused() rather than a reimplementation of it
* Fixed potential race between btrfs_handle_fully_remapped_bgs() and
btrfs_delete_unused_bgs()
* Non-async discard call to btrfs_handle_fully_remapped_bgs() moved from
transaction commit to cleaner thread
* Fixed reservation of SYSTEM chunk metadata
* Reservations now done before starting a transaction to mark a block group
fully remapped
* Some other niggles that Boris pointed out
Mark Harmstone (16):
btrfs: add definitions and constants for remap-tree
btrfs: add REMAP chunk type
btrfs: allow remapped chunks to have zero stripes
btrfs: remove remapped block groups from the free-space tree
btrfs: don't add metadata items for the remap tree to the extent tree
btrfs: add extended version of struct block_group_item
btrfs: allow mounting filesystems with remap-tree incompat flag
btrfs: redirect I/O for remapped block groups
btrfs: handle deletions from remapped block group
btrfs: handle setting up relocation of block group with remap-tree
btrfs: move existing remaps before relocating block group
btrfs: replace identity remaps with actual remaps when doing
relocations
btrfs: add do_remap param to btrfs_discard_extent()
btrfs: allow balancing remap tree
btrfs: handle discarding fully-remapped block groups
btrfs: populate fully_remapped_bgs_list on mount
fs/btrfs/Kconfig | 2 +
fs/btrfs/accessors.h | 29 +
fs/btrfs/bio.c | 3 +-
fs/btrfs/bio.h | 3 +
fs/btrfs/block-group.c | 306 ++++-
fs/btrfs/block-group.h | 25 +-
fs/btrfs/block-rsv.c | 8 +
fs/btrfs/block-rsv.h | 1 +
fs/btrfs/discard.c | 57 +-
fs/btrfs/disk-io.c | 125 +-
fs/btrfs/extent-tree.c | 129 ++-
fs/btrfs/extent-tree.h | 3 +-
fs/btrfs/free-space-cache.c | 78 +-
fs/btrfs/free-space-cache.h | 1 +
fs/btrfs/free-space-tree.c | 4 +-
fs/btrfs/free-space-tree.h | 5 +-
fs/btrfs/fs.h | 10 +-
fs/btrfs/inode.c | 2 +-
fs/btrfs/locking.c | 1 +
fs/btrfs/relocation.c | 1885 +++++++++++++++++++++++++++++--
fs/btrfs/relocation.h | 18 +
fs/btrfs/space-info.c | 22 +-
fs/btrfs/sysfs.c | 4 +
fs/btrfs/transaction.c | 7 +
fs/btrfs/tree-checker.c | 94 +-
fs/btrfs/tree-checker.h | 5 +
fs/btrfs/volumes.c | 356 +++++-
fs/btrfs/volumes.h | 18 +-
include/uapi/linux/btrfs.h | 1 +
include/uapi/linux/btrfs_tree.h | 29 +-
30 files changed, 2968 insertions(+), 263 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-14 18:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 18:47 Mark Harmstone [this message]
2025-11-14 18:47 ` [PATCH v6 01/16] btrfs: add definitions and constants for remap-tree Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 02/16] btrfs: add REMAP chunk type Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 03/16] btrfs: allow remapped chunks to have zero stripes Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 04/16] btrfs: remove remapped block groups from the free-space tree Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 05/16] btrfs: don't add metadata items for the remap tree to the extent tree Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 06/16] btrfs: add extended version of struct block_group_item Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 07/16] btrfs: allow mounting filesystems with remap-tree incompat flag Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 08/16] btrfs: redirect I/O for remapped block groups Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 09/16] btrfs: handle deletions from remapped block group Mark Harmstone
2025-11-20 0:17 ` Boris Burkov
2025-11-24 12:40 ` Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 10/16] btrfs: handle setting up relocation of block group with remap-tree Mark Harmstone
2025-11-15 14:52 ` Sun Yangkai
2025-11-24 18:01 ` Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 11/16] btrfs: move existing remaps before relocating block group Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 12/16] btrfs: replace identity remaps with actual remaps when doing relocations Mark Harmstone
2025-11-20 0:21 ` Boris Burkov
2025-11-14 18:47 ` [PATCH v6 13/16] btrfs: add do_remap param to btrfs_discard_extent() Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 14/16] btrfs: allow balancing remap tree Mark Harmstone
2025-11-14 18:47 ` [PATCH v6 15/16] btrfs: handle discarding fully-remapped block groups Mark Harmstone
2025-11-20 0:19 ` Boris Burkov
2025-11-14 18:47 ` [PATCH v6 16/16] btrfs: populate fully_remapped_bgs_list on mount Mark Harmstone
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=20251114184745.9304-1-mark@harmstone.com \
--to=mark@harmstone.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 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.