diff options
author | 2023-05-25 12:00:38 +0800 | |
---|---|---|
committer | 2023-05-25 10:46:53 -1000 | |
commit | 18c8ae813156a6855f026de80fffb91e1a28ab3d (patch) | |
tree | 8d41793c9775f9f18ef9c6b4c542c41d3d27eaf6 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | workqueue: Fix WARN_ON_ONCE() triggers in worker_enter_idle() (diff) | |
download | wireguard-linux-18c8ae813156a6855f026de80fffb91e1a28ab3d.tar.xz wireguard-linux-18c8ae813156a6855f026de80fffb91e1a28ab3d.zip |
workqueue: Disable per-cpu CPU hog detection when wq_cpu_intensive_thresh_us is 0
If workqueue.cpu_intensive_thresh_us is set to 0, the detection mechanism
for CPU-hogging per-cpu work item will keep triggering spuriously:
workqueue: process_srcu hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND
workqueue: gc_worker hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND
workqueue: gc_worker hogged CPU for >0us 8 times, consider switching to WQ_UNBOUND
workqueue: wait_rcu_exp_gp hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND
workqueue: kfree_rcu_monitor hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND
workqueue: kfree_rcu_monitor hogged CPU for >0us 8 times, consider switching to WQ_UNBOUND
workqueue: reg_todo hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND
This commit therefore disables the CPU-hog detection mechanism when
workqueue.cpu_intensive_thresh_us is set to 0.
tj: Patch description updated and the condition check on
cpu_intensive_thresh_us separated into a separate if statement for
readability.
Signed-off-by: Zqiang <qiang.zhang1211@gmail.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions