From: Nivedita Singhvi <niv@us.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: paulmck@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt11
Date: Tue, 16 Aug 2011 22:03:50 -0700 [thread overview]
Message-ID: <4E4B4BB6.7000400@us.ibm.com> (raw)
In-Reply-To: <1313555332.5605.7.camel@marge.simson.net>
Mike Galbraith wrote:
> On Tue, 2011-08-16 at 12:31 -0700, Paul E. McKenney wrote:
>> On Tue, Aug 16, 2011 at 05:10:08PM +0200, Mike Galbraith wrote:
>>> On Tue, 2011-08-16 at 07:17 -0700, Nivedita Singhvi wrote:
>>>
>>>> Mike,
>>>>
>>>> Which test were you running? Because I'm not seeing it
>>>> on our x3550 M3..
>>> -rt11 did not trip up just idling along like a couple earlier releases
>>> did, but did stall when I tried to run ltp realtime testcases.
>> But please note that if your realtime workload is CPU-bound with prio
>> greater than that of RCU_SOFTIRQ, stalls would be expected.
>
> The (broken) jitter testcase runs two threads, an interrupter thread at
> prio 80, and a worker at 10. Both sleep. I just ran the testcase
> standalone, and no stall happened, so perhaps something from an earlier
> testcase got stuck.. or something.
>
> I'll try maxing out boost, and see what happens. It was set to 50.
>
> -Mike
I suppose the other thing to watch out for is the stall
any RT task might see when sched_rt_runtime_us is maxed
out -- it was the occasional cause for a failure or two,
as well.
thanks,
Nivedita
next prev parent reply other threads:[~2011-08-17 5:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 10:53 [ANNOUNCE] 3.0.1-rt11 Peter Zijlstra
2011-08-13 11:48 ` Mike Galbraith
2011-08-13 11:58 ` Peter Zijlstra
2011-08-13 13:59 ` Mike Galbraith
2011-08-13 14:23 ` Peter Zijlstra
2011-08-13 16:27 ` Paul E. McKenney
2011-08-14 4:23 ` Mike Galbraith
2011-08-16 14:17 ` Nivedita Singhvi
2011-08-16 15:10 ` Mike Galbraith
2011-08-16 15:18 ` Nivedita Singhvi
2011-08-16 19:31 ` Paul E. McKenney
2011-08-17 4:28 ` Mike Galbraith
2011-08-17 5:03 ` Nivedita Singhvi [this message]
2011-08-15 10:09 ` Mike Galbraith
2011-08-14 21:19 ` Clark Williams
2011-08-23 14:12 ` [patch] sched, rt: fix migrate_enable() thinko Mike Galbraith
2011-09-08 2:11 ` Frank Rowand
2011-09-08 4:58 ` Mike Galbraith
2011-08-24 23:58 ` [ANNOUNCE] 3.0.1-rt11 Frank Rowand
2011-08-26 23:55 ` Paul E. McKenney
2011-08-29 19:57 ` Frank Rowand
2011-08-30 3:17 ` Paul E. McKenney
2011-09-07 2:53 ` Frank Rowand
2011-09-07 3:00 ` Frank Rowand
2011-09-07 6:42 ` Paul E. McKenney
2011-09-07 9:25 ` Thomas Gleixner
2011-09-07 10:46 ` Russell King - ARM Linux
2011-09-07 10:47 ` Russell King - ARM Linux
2011-09-07 10:57 ` Thomas Gleixner
2011-09-07 14:01 ` Russell King - ARM Linux
2011-09-07 16:32 ` Thomas Gleixner
2011-09-07 16:33 ` Frank Rowand
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=4E4B4BB6.7000400@us.ibm.com \
--to=niv@us.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--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).