From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs: some cleanups and minor optimization for log trees
Date: Thu, 13 Mar 2025 17:55:30 +0000 [thread overview]
Message-ID: <cover.1741887949.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
A series of cleanups, simplifications and a minor optimization related to
log replay and inode logging. Details in the change logs.
Filipe Manana (7):
btrfs: avoid unnecessary memory allocation and copy at overwrite_item()
btrfs: use variables to store extent buffer and slot at overwrite_item()
btrfs: update outdated comment for overwrite_item()
btrfs: use memcmp_extent_buffer() at replay_one_extent()
btrfs: remove redundant else statement from btrfs_log_inode_parent()
btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent()
btrfs: remove end_no_trans label from btrfs_log_inode_parent()
fs/btrfs/tree-log.c | 125 +++++++++++++++++++-------------------------
1 file changed, 53 insertions(+), 72 deletions(-)
--
2.45.2
next reply other threads:[~2025-03-13 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 17:55 fdmanana [this message]
2025-03-13 17:55 ` [PATCH 1/7] btrfs: avoid unnecessary memory allocation and copy at overwrite_item() fdmanana
2025-03-13 17:55 ` [PATCH 2/7] btrfs: use variables to store extent buffer and slot " fdmanana
2025-03-13 17:55 ` [PATCH 3/7] btrfs: update outdated comment for overwrite_item() fdmanana
2025-03-13 17:55 ` [PATCH 4/7] btrfs: use memcmp_extent_buffer() at replay_one_extent() fdmanana
2025-03-13 17:55 ` [PATCH 5/7] btrfs: remove redundant else statement from btrfs_log_inode_parent() fdmanana
2025-03-13 17:55 ` [PATCH 6/7] btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent() fdmanana
2025-03-13 17:55 ` [PATCH 7/7] btrfs: remove end_no_trans label from btrfs_log_inode_parent() fdmanana
2025-03-17 14:59 ` [PATCH 0/7] btrfs: some cleanups and minor optimization for log trees 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.1741887949.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.