From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs: cleanups and improvements around extent map release
Date: Wed, 17 Apr 2024 23:44:01 +0200 [thread overview]
Message-ID: <20240417214401.GV3492@twin.jikos.cz> (raw)
In-Reply-To: <cover.1713302470.git.fdmanana@suse.com>
On Wed, Apr 17, 2024 at 12:03:30PM +0100, fdmanana@kernel.org wrote:
> 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
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2024-04-17 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:03 [PATCH 0/5] btrfs: cleanups and improvements around extent map release fdmanana
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 ` David Sterba [this message]
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=20240417214401.GV3492@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).