From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rt3 + Open Posix Test Suite
Date: Tue, 10 Jan 2006 22:53:12 -0500 [thread overview]
Message-ID: <1136951593.6197.81.camel@localhost.localdomain> (raw)
In-Reply-To: <1136934210.5756.13.camel@localhost.localdomain>
On Tue, 2006-01-10 at 15:03 -0800, Daniel Walker wrote:
> It's worth noting that a few tests in the current Open Posix Test Suite
> hang RT systems.
>
> Specifically this test (hope this url comes through),
>
> http://cvs.sourceforge.net/viewcvs.py/*checkout*/posixtest/posixtestsuite/conformance/interfaces/sched_setparam/10-1.c?rev=1.2
>
> sched_setparam test 10-1.c and I think 9-1.c .
>
> The 10-1 test spawns some children at SCHED_FIFO priority 99 , then runs
> the following,
>
> void child_process(){
> alarm(2);
>
> while(1) {
> (*shmptr)++;
> sched_yield();
> }
> }
>
> I'm sure this is what's hanging the system, the yield() is one issue.
> Another is why the alarm() is never delivered .
This runs a while loop at SCHED_FIFO prio 99? And alarm never happens.
Doesn't the alarm get activated by the softirqd that is running at a
lower priority? Seems that this is starving out the softirq from
getting the alarm.
I believe that Thomas once had priorities attached to the timers. I'd
like to see that again, and may even start adding them myself, such that
when a process activates a timer, when that timer goes off, the softirq
will get the priority of the timer. But this has some complications to
be sorted out.
-- Steve
next prev parent reply other threads:[~2006-01-11 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 23:03 2.6.15-rt3 + Open Posix Test Suite Daniel Walker
2006-01-11 3:53 ` Steven Rostedt [this message]
2006-01-11 14:41 ` Daniel Walker
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=1136951593.6197.81.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).