Thread (10 messages) 10 messages, 5 authors, 2012-03-03

Re: [RFC PATCH] kick ksoftirqd more often to please soft lockup detector

From: Dan Williams <hidden>
Date: 2012-02-28 16:48:41
Also in: lkml

On Tue, Feb 28, 2012 at 1:48 AM, Peter Zijlstra [off-list ref] wrote:
quoted
BUG: soft lockup - CPU#3 stuck for 22s! [kworker/3:1:78]
So you're stuck in softirq for 22s+, max_restart is 10, this gives that
on average you spend 2.2s+ per softirq invocation, this is completely
absolutely bonkers. Softirq handlers should never consume significant
amount of cpu-time.
I'm not sure whether this was just one __do_softirq() invocation, or
multiple.  I'll see if I can instrument this, but the suspicion is
that max_restart can't help when softirq is constantly re-triggered.
I'll also add the below patch to see if any single invocation is
violating these expectations.

--
Dan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help