From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs: cleanups and improvements around extent map release
Date: Wed, 17 Apr 2024 12:03:30 +0100 [thread overview]
Message-ID: <cover.1713302470.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
These make the folio release path release extent maps more often when they
are not needed, as well as some cleanups. More details in the change logs.
Filipe Manana (5):
btrfs: rename some variables at try_release_extent_mapping()
btrfs: use btrfs_get_fs_generation() at try_release_extent_mapping()
btrfs: remove i_size restriction at try_release_extent_mapping()
btrfs: be better releasing extent maps at try_release_extent_mapping()
btrfs: make try_release_extent_mapping() return a bool
fs/btrfs/extent_io.c | 149 +++++++++++++++++++++----------------------
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/inode.c | 7 +-
3 files changed, 77 insertions(+), 81 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-17 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:03 fdmanana [this message]
2024-04-17 11:03 ` [PATCH 1/5] btrfs: rename some variables at try_release_extent_mapping() fdmanana
2024-04-17 11:21 ` Johannes Thumshirn
2024-04-17 11:03 ` [PATCH 2/5] btrfs: use btrfs_get_fs_generation() " fdmanana
2024-04-17 11:22 ` Johannes Thumshirn
2024-04-17 11:03 ` [PATCH 3/5] btrfs: remove i_size restriction " fdmanana
2024-04-17 11:23 ` Johannes Thumshirn
2024-04-17 11:03 ` [PATCH 4/5] btrfs: be better releasing extent maps " fdmanana
2024-04-17 11:28 ` Johannes Thumshirn
2024-04-17 11:03 ` [PATCH 5/5] btrfs: make try_release_extent_mapping() return a bool fdmanana
2024-04-17 11:27 ` Johannes Thumshirn
2024-04-17 21:44 ` [PATCH 0/5] btrfs: cleanups and improvements around extent map release 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.1713302470.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.