From: Sven-Thorsten Dietrich <thebigcorporation@gmail.com>
To: Peter LaDow <petela@gocougs.wsu.edu>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Interrupt Bottom Half Scheduling
Date: Mon, 14 Feb 2011 15:04:03 -0800 [thread overview]
Message-ID: <1297724643.10271.16.camel@quadrophenia> (raw)
In-Reply-To: <AANLkTimGobdGMgnc8bVJTvYtH4Tjn2ZVmroeFA2s06WD@mail.gmail.com>
On Mon, 2011-02-14 at 14:31 -0800, Peter LaDow wrote:
> How is the scheduling of the hrtimers softirq thread handled?
>
> When querying the RT priority of the hrtimer softirq, I get a priority
> of 50. But when running a priority 99 thread, we still seem to be
> getting interrupted. Shouldn't the hrtimer softirq be put off until
> the CPU is idle or a lower priority task is running?
Does your prio 99 thread perhaps encounter a prio inversion dependency
on one of the softriq threads?
>
> Thanks,
> Pete
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-14 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 22:31 Interrupt Bottom Half Scheduling Peter LaDow
2011-02-14 23:04 ` Sven-Thorsten Dietrich [this message]
2011-02-14 23:08 ` Peter LaDow
2011-02-14 23:35 ` Sven-Thorsten Dietrich
2011-02-14 23:42 ` Peter LaDow
2011-02-15 0:50 ` Sven-Thorsten Dietrich
2011-02-14 23:30 ` Frank Rowand
2011-02-15 1:10 ` Peter LaDow
2011-02-15 1:58 ` Frank Rowand
2011-02-15 2:16 ` Frank Rowand
2011-02-15 16:42 ` Peter LaDow
2011-02-15 18:38 ` Frank Rowand
2011-02-15 18:40 ` Frank Rowand
2011-02-15 19:12 ` Peter LaDow
2011-02-15 19:35 ` Frank Rowand
2011-02-16 20:18 ` Peter LaDow
2011-02-15 8:40 ` Armin Steinhoff
2011-02-15 8:23 ` Uwe Kleine-König
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=1297724643.10271.16.camel@quadrophenia \
--to=thebigcorporation@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=petela@gocougs.wsu.edu \
/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).