From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: sedat.dilek@gmail.com, Paul McKenney <paul.mckenney@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-next <linux-next@vger.kernel.org>
Subject: Re: [next-20120823] NOHZ: local_softirq_pending 200 on s/r
Date: Fri, 24 Aug 2012 07:52:47 -0700 [thread overview]
Message-ID: <20120824145247.GB2472@linux.vnet.ibm.com> (raw)
In-Reply-To: <1345793168.4331.64.camel@marge.simpson.net>
On Fri, Aug 24, 2012 at 09:26:08AM +0200, Mike Galbraith wrote:
> On Thu, 2012-08-23 at 12:04 +0200, Sedat Dilek wrote:
>
> > Jack Winter confirmed to see similiar NOHZ messages also on
> > v3.4.9-rt17 kernel (CPU: Core2Duo when no suspend performed):
> >
> > [15223.171585] NOHZ: local_softirq_pending 08
>
> These can be caused by blocking while holding local_softirq_lock.
>
> Even with per softirq threads, and then (yet more overhead) splitting
> the lock to make sure one softirq type can't block another, _and_ only
> griping if the lock for the pending softirq is _not_ held, seems the
> little bugger can still be triggered very rarely by syn flood induced
> handler bail/raise. Annoying little gripe :)
Hmmm... Now that you mention it, if I understand correctly, the
conversion of spinlocks to sleeplocks in -rt would seem to invalidate
this particular diagnostic completely.
So, what am I missing?
Thanx, Paul
next prev parent reply other threads:[~2012-08-24 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 10:04 [next-20120823] NOHZ: local_softirq_pending 200 on s/r Sedat Dilek
2012-08-23 10:46 ` Thomas Gleixner
2012-08-23 15:43 ` Paul E. McKenney
2012-08-23 16:06 ` Sedat Dilek
2012-08-23 17:14 ` Paul E. McKenney
2012-08-23 18:55 ` Sedat Dilek
2012-08-23 19:09 ` Paul E. McKenney
2012-08-24 7:26 ` Mike Galbraith
2012-08-24 14:52 ` Paul E. McKenney [this message]
2012-08-24 15:40 ` Thomas Gleixner
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=20120824145247.GB2472@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.mckenney@linaro.org \
--cc=sedat.dilek@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).