From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore
Date: Wed, 07 Jan 2026 03:30:12 +0000 [thread overview]
Message-ID: <176775661252.2218650.8734034218364835852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260104020729.1064529-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 4 Jan 2026 10:07:16 +0800 you wrote:
> This patch adds lock elapsed time trace facility for f2fs rwsemphore.
>
> If total elapsed time of critical region covered by lock exceeds a
> threshold, it will print tracepoint to dump information of lock related
> context, including:
> - thread information
> - CPU/IO priority
> - lock information
> - elapsed time
> - total time
> - running time (depend on CONFIG_64BIT)
> - runnable time (depend on CONFIG_SCHED_INFO and CONFIG_SCHEDSTATS)
> - io sleep time (depend on CONFIG_TASK_DELAY_ACCT and
> /proc/sys/kernel/task_delayacct)
> - other time (by default other time will account nonio sleep time,
> but, if above kconfig is not defined, other time will
> include runnable time and/or io sleep time as wll)
>
> [...]
Here is the summary with links:
- [f2fs-dev,01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore
https://git.kernel.org/jaegeuk/f2fs/c/79b3cebc70fc
- [f2fs-dev,02/14] f2fs: sysfs: introduce max_lock_elapsed_time
https://git.kernel.org/jaegeuk/f2fs/c/e4b75621fc43
- [f2fs-dev,03/14] f2fs: trace elapsed time for cp_rwsem lock
https://git.kernel.org/jaegeuk/f2fs/c/66e9e0d55d11
- [f2fs-dev,04/14] f2fs: trace elapsed time for node_change lock
https://git.kernel.org/jaegeuk/f2fs/c/f9f93602512b
- [f2fs-dev,05/14] f2fs: trace elapsed time for node_write lock
https://git.kernel.org/jaegeuk/f2fs/c/bb28b66875cc
- [f2fs-dev,06/14] f2fs: trace elapsed time for gc_lock lock
(no matching commit)
- [f2fs-dev,07/14] f2fs: trace elapsed time for cp_global_sem lock
https://git.kernel.org/jaegeuk/f2fs/c/ce9fe67c9cdb
- [f2fs-dev,08/14] f2fs: trace elapsed time for io_rwsem lock
https://git.kernel.org/jaegeuk/f2fs/c/67972c2b8974
- [f2fs-dev,09/14] f2fs: clean up w/ __f2fs_schedule_timeout()
https://git.kernel.org/jaegeuk/f2fs/c/b5da276ae6ab
- [f2fs-dev,10/14] f2fs: fix to use jiffies based precision for DEFAULT_SCHEDULE_TIMEOUT
https://git.kernel.org/jaegeuk/f2fs/c/da90b6715567
- [f2fs-dev,11/14] f2fs: fix timeout precision of f2fs_io_schedule_timeout_killable()
https://git.kernel.org/jaegeuk/f2fs/c/6fa116053951
- [f2fs-dev,12/14] f2fs: rename FAULT_TIMEOUT to FAULT_ATOMIC_TIMEOUT
https://git.kernel.org/jaegeuk/f2fs/c/7a127c80b0ee
- [f2fs-dev,13/14] f2fs: introduce FAULT_LOCK_TIMEOUT
https://git.kernel.org/jaegeuk/f2fs/c/c56254e2e042
- [f2fs-dev,14/14] f2fs: sysfs: introduce inject_lock_timeout
https://git.kernel.org/jaegeuk/f2fs/c/d36de29f4bb5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-07 3:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 2:07 Chao Yu
2026-01-04 2:07 ` [PATCH 02/14] f2fs: sysfs: introduce max_lock_elapsed_time Chao Yu
2026-01-04 2:07 ` [PATCH 03/14] f2fs: trace elapsed time for cp_rwsem lock Chao Yu
2026-01-04 2:07 ` [PATCH 04/14] f2fs: trace elapsed time for node_change lock Chao Yu
2026-01-04 2:07 ` [PATCH 05/14] f2fs: trace elapsed time for node_write lock Chao Yu
2026-01-04 2:07 ` [PATCH 06/14] f2fs: trace elapsed time for gc_lock lock Chao Yu
2026-01-04 5:35 ` Jaegeuk Kim
2026-01-04 5:42 ` Jaegeuk Kim
2026-01-04 6:27 ` Chao Yu
2026-01-04 2:07 ` [PATCH 07/14] f2fs: trace elapsed time for cp_global_sem lock Chao Yu
2026-01-04 2:07 ` [PATCH 08/14] f2fs: trace elapsed time for io_rwsem lock Chao Yu
2026-01-04 2:07 ` [PATCH 09/14] f2fs: clean up w/ __f2fs_schedule_timeout() Chao Yu
2026-01-04 2:07 ` [PATCH 10/14] f2fs: fix to use jiffies based precision for DEFAULT_SCHEDULE_TIMEOUT Chao Yu
2026-01-04 2:07 ` [PATCH 11/14] f2fs: fix timeout precision of f2fs_io_schedule_timeout_killable() Chao Yu
2026-01-04 2:07 ` [PATCH 12/14] f2fs: rename FAULT_TIMEOUT to FAULT_ATOMIC_TIMEOUT Chao Yu
2026-01-04 2:07 ` [PATCH 13/14] f2fs: introduce FAULT_LOCK_TIMEOUT Chao Yu
2026-01-04 2:07 ` [PATCH 14/14] f2fs: sysfs: introduce inject_lock_timeout Chao Yu
2026-01-04 5:28 ` [PATCH 01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore Jaegeuk Kim
2026-01-07 3:30 ` patchwork-bot+f2fs [this message]
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=176775661252.2218650.8734034218364835852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®