workqueue: Track and monitor per-workqueue CPU time usage
authorTejun Heo <tj@kernel.org>
Thu, 18 May 2023 03:02:09 +0000 (17:02 -1000)
committerTejun Heo <tj@kernel.org>
Thu, 18 May 2023 03:02:09 +0000 (17:02 -1000)
commit8a1dd1e547c1a037692e7a6da6a76108108c72b1
tree8441f7c4e566a76ecc0bb4d94091d0997f05f8f4
parent6363845005202148b8409ec3082e80845c19d309
workqueue: Track and monitor per-workqueue CPU time usage

Now that wq_worker_tick() is there, we can easily track the rough CPU time
consumption of each workqueue by charging the whole tick whenever a tick
hits an active workqueue. While not super accurate, it provides reasonable
visibility into the workqueues that consume a lot of CPU cycles.
wq_monitor.py is updated to report the per-workqueue CPU times.

v2: wq_monitor.py was using "cputime" as the key when outputting in json
    format. Use "cpu_time" instead for consistency with other fields.

Signed-off-by: Tejun Heo <tj@kernel.org>
Documentation/core-api/workqueue.rst
kernel/workqueue.c
tools/workqueue/wq_monitor.py