From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel-rt <linux-rt-users@vger.kernel.org>,
Mark Hounschell <markh@compro.net>
Subject: Re: timer signal loss on RT
Date: Sat, 10 Mar 2012 06:53:31 -0500 [thread overview]
Message-ID: <4F5B40BB.9080305@cfl.rr.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1203101231230.2742@ionos>
On 03/10/2012 06:34 AM, Thomas Gleixner wrote:
> On Sat, 10 Mar 2012, Mark Hounschell wrote:
>> I'm sure you can find many things wrong with this test case but I'm not
>> sending it for discussion on the merits, or certainly the lack of, an
>> application that contains a cpu hog, but only to show what I think is a
>> problem with RT kernels.
>
> Nope, PEBKAC.
>
> Timer signals are delivered via ksoftirqd, so your cpu hog prevents
> ksoftirqd frum running.
>
Does ksoftirqd deliver timer signals in vanilla?
Thanks
Mark
next prev parent reply other threads:[~2012-03-10 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 10:26 timer signal loss on RT Mark Hounschell
2012-03-10 11:08 ` Mike Galbraith
2012-03-10 11:34 ` Thomas Gleixner
2012-03-10 11:53 ` Mark Hounschell [this message]
2012-03-10 19:44 ` Steven Rostedt
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=4F5B40BB.9080305@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=markh@compro.net \
--cc=tglx@linutronix.de \
/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