From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/2] Convert btrfs_root::delayed_nodes_tree to xarray
Date: Thu, 30 Nov 2023 23:49:06 +0100 [thread overview]
Message-ID: <cover.1701384168.git.dsterba@suse.com> (raw)
This restarts the radix-tree to xarray conversion that we had to revert.
There are two more structures to convert, possibly with also spinlock to
mutex conversions needed (buffer_radix and fs_roots_radix), but for the
buffer radix I don't want to do now as we have the folio conversion
ongoing. The fs_roots will most likely need the lock conversion so
that's a change that I want to take the whole dev cycle, planned for 6.9.
David Sterba (2):
btrfs: drop radix-tree preload from btrfs_get_or_create_delayed_node()
btrfs: use xarray for btrfs_root::delayed_nodes_tree instead of
radix-tree
fs/btrfs/ctree.h | 6 +--
fs/btrfs/delayed-inode.c | 86 +++++++++++++++++++---------------------
fs/btrfs/disk-io.c | 3 +-
fs/btrfs/inode.c | 2 +-
4 files changed, 47 insertions(+), 50 deletions(-)
--
2.42.1
next reply other threads:[~2023-11-30 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 22:49 David Sterba [this message]
2023-11-30 22:49 ` [PATCH 1/2] btrfs: drop radix-tree preload from btrfs_get_or_create_delayed_node() David Sterba
2023-11-30 22:49 ` [PATCH 2/2] btrfs: use xarray for btrfs_root::delayed_nodes_tree instead of radix-tree David Sterba
2023-12-01 11:03 ` Filipe Manana
2023-12-04 15:49 ` David Sterba
2023-12-04 16:07 ` David Sterba
2023-12-05 19:04 ` David Sterba
2023-12-05 19:39 ` 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=cover.1701384168.git.dsterba@suse.com \
--to=dsterba@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