From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] btrfs: trace: Trace events for btrfs tree locking
Date: Mon, 15 Apr 2019 21:15:23 +0800 [thread overview]
Message-ID: <20190415131525.20274-1-wqu@suse.com> (raw)
This branch can be fetched from github:
https://github.com/adam900710/linux/tree/trace_locking
Which is based on v5.1-rc4 tag.
This patchset will introduce the following trace events for corresponding
functions:
btrfs_tree_lock (sleepable)
btrfs_tree_unlock
btrfs_tree_read_lock (sleepable)
btrfs_tree_read_unlock
btrfs_tree_read_unlock_blocking
btrfs_set_lock_blocking_read
btrfs_set_lock_blocking_write
btrfs_clear_lock_blocking_read
btrfs_clear_lock_blocking_write
btrfs_try_tree_read_lock
btrfs_try_tree_write_lock
btrfs_tree_read_lock_atomic
The two sleepable ones will have extra info like start_ns, end_ns,
diff_ns.
Those two can be specially useful for tree lock wait time.
There is tool to utilize those two events already:
https://github.com/adam900710/btrfs-profiler/blob/master/tree_lock_wait.py
The non-sleepable can be useful for possible user space based lock
leakage/dead lock detector.
Changelog:
v2:
- Hide all ktime_get_ns() call out of trace events
So there will be no overhead if trace events are not enabled.
v3:
- More output for human to take a glance
- More trace events for later bcc usage
Like lock leakage and deadlock detection.
Qu Wenruo (2):
btrfs: trace: Introduce trace events for sleepable tree lock
btrfs: trace: Introduce trace events for all btrfs tree locking events
fs/btrfs/locking.c | 22 +++++++++
include/trace/events/btrfs.h | 86 ++++++++++++++++++++++++++++++++++++
2 files changed, 108 insertions(+)
--
2.21.0
next reply other threads:[~2019-04-15 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 13:15 Qu Wenruo [this message]
2019-04-15 13:15 ` [PATCH v3 1/2] btrfs: trace: Introduce trace events for sleepable tree lock Qu Wenruo
2019-04-15 13:15 ` [PATCH v3 2/2] btrfs: trace: Introduce trace events for all btrfs tree locking events Qu Wenruo
2019-04-15 14:28 ` [PATCH v3 0/2] btrfs: trace: Trace events for btrfs tree locking 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=20190415131525.20274-1-wqu@suse.com \
--to=wqu@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).