From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/10] btrfs: set of small optimizations for inode logging
Date: Tue, 31 Aug 2021 15:30:30 +0100 [thread overview]
Message-ID: <cover.1630419897.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
The following patchset adds a few optimizations for inode logging, along
with some necessary refactorings/cleanups to be able to implement them.
Test results are in the change log of the last patch.
Filipe Manana (10):
btrfs: check if a log tree exists at inode_logged()
btrfs: remove no longer needed checks for NULL log context
btrfs: do not log new dentries when logging that a new name exists
btrfs: always update the logged transaction when logging new names
btrfs: avoid expensive search when dropping inode items from log
btrfs: add helper to truncate inode items when logging inode
btrfs: avoid expensive search when truncating inode items from the log
btrfs: avoid search for logged i_size when logging inode if possible
btrfs: avoid attempt to drop extents when logging inode for the first time
btrfs: do not commit delayed inode when logging a file in full sync mode
fs/btrfs/tree-log.c | 208 +++++++++++++++++++++++---------------------
1 file changed, 110 insertions(+), 98 deletions(-)
--
2.28.0
next reply other threads:[~2021-08-31 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 14:30 fdmanana [this message]
2021-08-31 14:30 ` [PATCH 01/10] btrfs: check if a log tree exists at inode_logged() fdmanana
2021-08-31 14:30 ` [PATCH 02/10] btrfs: remove no longer needed checks for NULL log context fdmanana
2021-08-31 14:30 ` [PATCH 03/10] btrfs: do not log new dentries when logging that a new name exists fdmanana
2021-08-31 14:30 ` [PATCH 04/10] btrfs: always update the logged transaction when logging new names fdmanana
2021-08-31 14:30 ` [PATCH 05/10] btrfs: avoid expensive search when dropping inode items from log fdmanana
2021-08-31 14:30 ` [PATCH 06/10] btrfs: add helper to truncate inode items when logging inode fdmanana
2021-08-31 14:30 ` [PATCH 07/10] btrfs: avoid expensive search when truncating inode items from the log fdmanana
2021-08-31 14:30 ` [PATCH 08/10] btrfs: avoid search for logged i_size when logging inode if possible fdmanana
2021-08-31 14:30 ` [PATCH 09/10] btrfs: avoid attempt to drop extents when logging inode for the first time fdmanana
2021-08-31 14:30 ` [PATCH 10/10] btrfs: do not commit delayed inode when logging a file in full sync mode fdmanana
2021-09-02 16:56 ` [PATCH 00/10] btrfs: set of small optimizations for inode logging 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.1630419897.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