public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org, linux-rt@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: NOHZ: local_softirq_pending 10
Date: Thu, 11 Jun 2009 17:12:00 +0200	[thread overview]
Message-ID: <1244733120.6691.433.camel@laptop> (raw)
In-Reply-To: <4A311D2A.808@xs4all.nl>

On Thu, 2009-06-11 at 17:05 +0200, Udo van den Heuvel wrote:
> Hello,
> 
> I found a few of these in my 2.6.29.4-rt16 logs:
> 
> NOHZ: local_softirq_pending 10
> 
> Are they rt-related?
> (I saw them in older kernels without -rt as well)
> How serious? How to fix?

Not really serious, but curious, that appears to be BLOCK_SOFTIRQ, and
the only one I suspected to trigger this would be HRTIMER_SOFTIRQ.


      reply	other threads:[~2009-06-11 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 15:05 NOHZ: local_softirq_pending 10 Udo van den Heuvel
2009-06-11 15:12 ` Peter Zijlstra [this message]

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=1244733120.6691.433.camel@laptop \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=udovdh@xs4all.nl \
    /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