From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/11] btrfs: some cleanups and optimizations for extent maps
Date: Mon, 4 Dec 2023 16:20:22 +0000 [thread overview]
Message-ID: <cover.1701706418.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
These do some cleanups around extent maps and their tests, as well as
some optimizations. These are part of a larger work around extent maps,
but as they are fairly independent and the remainder will take a longer
while, sending these out separately. More details on the change logs.
Filipe Manana (11):
btrfs: assert extent map is not in a list when setting it up
btrfs: tests: fix error messages for test case 4 of extent map tests
btrfs: tests: do not ignore NULL extent maps for extent maps tests
btrfs: tests: print all values as decimal in messages for extent map tests
btrfs: unexport add_extent_mapping()
btrfs: remove redundant value assignment at btrfs_add_extent_mapping()
btrfs: log messages at unpin_extent_range() during unexpected cases
btrfs: avoid useless rbtree iterations when attempting to merge extent map
btrfs: make extent_map_end() argument const
btrfs: refactor mergable_maps() for more readability
btrfs: use the flags of an extent map to identify the compression type
fs/btrfs/compression.c | 4 +-
fs/btrfs/defrag.c | 8 +-
fs/btrfs/extent_io.c | 13 ++-
fs/btrfs/extent_map.c | 139 ++++++++++++++++--------------
fs/btrfs/extent_map.h | 64 +++++++++++---
fs/btrfs/file-item.c | 9 +-
fs/btrfs/file.c | 10 +--
fs/btrfs/inode.c | 35 ++++----
fs/btrfs/relocation.c | 2 +-
fs/btrfs/tests/extent-map-tests.c | 103 +++++++++++++---------
fs/btrfs/tests/inode-tests.c | 60 ++++++-------
fs/btrfs/tree-log.c | 16 ++--
include/trace/events/btrfs.h | 21 +++--
13 files changed, 272 insertions(+), 212 deletions(-)
--
2.40.1
next reply other threads:[~2023-12-04 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 16:20 fdmanana [this message]
2023-12-04 16:20 ` [PATCH 01/11] btrfs: assert extent map is not in a list when setting it up fdmanana
2023-12-04 16:20 ` [PATCH 02/11] btrfs: tests: fix error messages for test case 4 of extent map tests fdmanana
2023-12-04 16:20 ` [PATCH 03/11] btrfs: tests: do not ignore NULL extent maps for extent maps tests fdmanana
2023-12-04 16:20 ` [PATCH 04/11] btrfs: tests: print all values as decimal in messages for extent map tests fdmanana
2023-12-04 16:20 ` [PATCH 05/11] btrfs: unexport add_extent_mapping() fdmanana
2023-12-04 16:20 ` [PATCH 06/11] btrfs: remove redundant value assignment at btrfs_add_extent_mapping() fdmanana
2023-12-04 16:20 ` [PATCH 07/11] btrfs: log messages at unpin_extent_range() during unexpected cases fdmanana
2023-12-04 16:20 ` [PATCH 08/11] btrfs: avoid useless rbtree iterations when attempting to merge extent map fdmanana
2023-12-04 16:20 ` [PATCH 09/11] btrfs: make extent_map_end() argument const fdmanana
2023-12-04 16:20 ` [PATCH 10/11] btrfs: refactor mergable_maps() for more readability fdmanana
2023-12-04 16:20 ` [PATCH 11/11] btrfs: use the flags of an extent map to identify the compression type fdmanana
2023-12-05 14:43 ` David Sterba
2023-12-05 15:01 ` Filipe Manana
2023-12-05 15:00 ` David Sterba
2023-12-05 15:58 ` [PATCH 00/11] btrfs: some cleanups and optimizations for extent maps 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.1701706418.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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.