From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: some fsync updates when logging directories
Date: Wed, 5 Apr 2023 18:51:28 +0100 [thread overview]
Message-ID: <cover.1680716778.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Two optimizations for directory logging, more details on the changelogs.
Filipe Manana (2):
btrfs: avoid iterating over all indexes when logging directory
btrfs: use log root when iterating over index keys when logging directory
fs/btrfs/btrfs_inode.h | 32 +++++++++++++++---
fs/btrfs/tree-log.c | 76 +++++++++++++++++++++++++++---------------
2 files changed, 77 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-05 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 17:51 fdmanana [this message]
2023-04-05 17:51 ` [PATCH 1/2] btrfs: avoid iterating over all indexes when logging directory fdmanana
2023-04-06 15:24 ` David Sterba
2023-04-05 17:51 ` [PATCH 2/2] btrfs: use log root when iterating over index keys " fdmanana
2023-04-06 18:52 ` [PATCH 0/2] btrfs: some fsync updates when logging directories 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.1680716778.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