From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: andi@firstfloor.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: NMI watchdog + NOHZ question
Date: Wed, 24 Jun 2009 09:15:55 +0200 [thread overview]
Message-ID: <20090624071555.GK6760@one.firstfloor.org> (raw)
In-Reply-To: <20090624.000811.118222188.davem@davemloft.net>
On Wed, Jun 24, 2009 at 12:08:11AM -0700, David Miller wrote:
> From: Andi Kleen <andi@firstfloor.org>
> Date: Wed, 24 Jun 2009 09:03:15 +0200
>
> >> I'm not exactly sure what to do about this.
> >
> > Ack the timer interrupt earlier (and also give it a high priority?)
>
> It has a higher priority, but all interrupts get re-enabled right
> before we process software interrupts. So the flood of qla2xxx
> interrupts can come in before we can run the timer softirq and
> thus schedule the next timer interrupt.
Ah you have a one shot timer and it gets rescheduled in the softirq?
If yes why not in doing that directly in the hardirq handler?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-06-24 7:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 7:27 NMI watchdog + NOHZ question David Miller
2009-06-22 8:18 ` Andi Kleen
2009-06-22 9:27 ` David Miller
2009-06-24 0:17 ` David Miller
2009-06-24 7:03 ` Andi Kleen
2009-06-24 7:08 ` David Miller
2009-06-24 7:15 ` Andi Kleen [this message]
2009-06-24 7:17 ` David Miller
2009-06-24 7:53 ` Andi Kleen
2009-06-24 8:51 ` David Miller
2009-06-24 9:44 ` David Miller
2009-06-24 10:23 ` Andi Kleen
2009-06-24 10:32 ` David Miller
2009-06-24 10:52 ` Andi Kleen
2009-06-24 10:59 ` David Miller
2009-06-24 11:10 ` Andi Kleen
2009-09-03 9:36 ` David Miller
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=20090624071555.GK6760@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.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