From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: a few fsync related minor improvements and a cleanup
Date: Tue, 20 Jul 2021 16:03:39 +0100 [thread overview]
Message-ID: <cover.1626791500.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
The following patches remove some unnecessary code and bring a couple minor
performance improvements in the fsync path. They are independent of each other,
but are grouped in the same pathset just because they relate around the same
code. The last patch has some performance results in its changelog.
Filipe Manana (4):
btrfs: remove racy and unnecessary inode transaction update when using
no-holes
btrfs: avoid unnecessary log mutex contention when syncing log
btrfs: remove unnecessary list head initialization when syncing log
btrfs: avoid unnecessary lock and leaf splits when updating inode in
the log
fs/btrfs/inode.c | 12 ++++------
fs/btrfs/tree-log.c | 56 ++++++++++++++++++++++++++++++++++++---------
2 files changed, 50 insertions(+), 18 deletions(-)
--
2.30.2
next reply other threads:[~2021-07-20 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 15:03 fdmanana [this message]
2021-07-20 15:03 ` [PATCH 1/4] btrfs: remove racy and unnecessary inode transaction update when using no-holes fdmanana
2021-07-20 15:03 ` [PATCH 2/4] btrfs: avoid unnecessary log mutex contention when syncing log fdmanana
2021-07-20 15:03 ` [PATCH 3/4] btrfs: remove unnecessary list head initialization " fdmanana
2021-07-23 6:20 ` Nikolay Borisov
2021-07-23 8:11 ` Filipe Manana
2021-07-20 15:03 ` [PATCH 4/4] btrfs: avoid unnecessary lock and leaf splits when updating inode in the log fdmanana
2021-07-21 19:50 ` [PATCH 0/4] btrfs: a few fsync related minor improvements and a cleanup Josef Bacik
2021-07-22 13:55 ` 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.1626791500.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.