From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: a couple fixes for extent map merging and defrag
Date: Tue, 29 Oct 2024 17:22:42 +0000 [thread overview]
Message-ID: <cover.1730220532.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Some fixes for extent map merging not happened when it should (which avoids
saving some memory) and defrag not merging contiguous extents when it should
due to merged extent maps. Details in the change logs.
Filipe Manana (2):
btrfs: fix extent map merging not happening for adjacent extents
btrfs: fix defrag not merging contiguous extents due to merged extent maps
fs/btrfs/defrag.c | 10 +++++-----
fs/btrfs/extent_map.c | 7 ++++++-
2 files changed, 11 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2024-10-29 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 17:22 fdmanana [this message]
2024-10-29 17:22 ` [PATCH 1/2] btrfs: fix extent map merging not happening for adjacent extents fdmanana
2024-10-30 0:47 ` Anand Jain
2024-10-30 7:41 ` Filipe Manana
2024-10-29 17:22 ` [PATCH 2/2] btrfs: fix defrag not merging contiguous extents due to merged extent maps fdmanana
2024-10-30 7:57 ` [PATCH 0/2] btrfs: a couple fixes for extent map merging and defrag Qu Wenruo
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.1730220532.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox