From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs: some minor log tree updates
Date: Wed, 17 May 2023 12:02:11 +0100 [thread overview]
Message-ID: <cover.1684320689.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Add two optimizations to avoid falling back to transaction commits after
an inode is evicted and some cleanups. More details on the changelogs.
Filipe Manana (5):
btrfs: use inode_logged() at need_log_inode()
btrfs: use inode_logged() at btrfs_record_unlink_dir()
btrfs: update comments at btrfs_record_unlink_dir() to be more clear
btrfs: remove pointless label and goto at btrfs_record_unlink_dir()
btrfs: change for_rename argument of btrfs_record_unlink_dir() to bool
fs/btrfs/inode.c | 8 ++++----
fs/btrfs/tree-log.c | 34 +++++++++++++++++-----------------
fs/btrfs/tree-log.h | 2 +-
3 files changed, 22 insertions(+), 22 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-17 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 11:02 fdmanana [this message]
2023-05-17 11:02 ` [PATCH 1/5] btrfs: use inode_logged() at need_log_inode() fdmanana
2023-05-17 11:02 ` [PATCH 2/5] btrfs: use inode_logged() at btrfs_record_unlink_dir() fdmanana
2023-05-17 11:02 ` [PATCH 3/5] btrfs: update comments at btrfs_record_unlink_dir() to be more clear fdmanana
2023-05-17 11:02 ` [PATCH 4/5] btrfs: remove pointless label and goto at btrfs_record_unlink_dir() fdmanana
2023-05-17 11:02 ` [PATCH 5/5] btrfs: change for_rename argument of btrfs_record_unlink_dir() to bool fdmanana
2023-05-19 4:15 ` Anand Jain
2023-05-22 11:20 ` [PATCH 0/5] btrfs: some minor log tree updates 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.1684320689.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.