linux-kernel - High context switch rate, ksoftirqd's chewing cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <50A78AA9.5040904@iskon.hr>
Date:	Sat, 17 Nov 2012 14:01:29 +0100
From:	Zlatko Calusic <zlatko.calusic@...on.hr>
To:	Tejun Heo <tj@...nel.org>
CC:	linux-kernel@...r.kernel.org
Subject: High context switch rate, ksoftirqd's chewing cpu

Hello Tejun et al.

This week I spent some hours tracking a regression in 3.7 kernel that 
was producing high context switch rate on one of my machines. I 
carefully bisected between 3.6 and 3.7-rc1 and eventually found this 
commit a culprit:

commit e7c2f967445dd2041f0f8e3179cca22bb8bb7f79
Author: Tejun Heo <tj@...nel.org>
Date:   Tue Aug 21 13:18:24 2012 -0700

     workqueue: use mod_delayed_work() instead of __cancel + queue

     Now that mod_delayed_work() is safe to call from IRQ handlers,
     __cancel_delayed_work() followed by queue_delayed_work() can be
     replaced with mod_delayed_work().

     Most conversions are straight-forward except for the following.

     * net/core/link_watch.c: linkwatch_schedule_work() was doing a quite
       elaborate dancing around its delayed_work.  Collapse it such that
       linkwatch_work is queued for immediate execution if LW_URGENT and
       existing timer is kept otherwise.

     Signed-off-by: Tejun Heo <tj@...nel.org>
     Cc: "David S. Miller" <davem@...emloft.net>
     Cc: Tomi Valkeinen <tomi.valkeinen@...com>

Then I carefully reverted chunk by chunk to find out what exact change 
is responsible for the regression. You can find it attached as wq.patch 
(to preserve whitespace). Very simple modification with wildly different 
behavior on only one of my machines, weird. I'm also attaching ctxt/s 
graph that shows the impact nicely. I'll gladly provide any additional 
info that could help you resolve this.

Please Cc: on reply (not subscribed to lkml).

Regards,
-- 
Zlatko

View attachment "wq.patch" of type "text/x-patch" (521 bytes)

Download attachment "context-weekly.png" of type "image/png" (11787 bytes)