From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: Linux RT Users <linux-rt-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Jean Pierre Dion <jean-pierre.dion@bull.net>,
Darren Hart <dvhltc@us.ibm.com>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH RT] Fix RT balancing tasks pulling
Date: Tue, 31 Jul 2007 13:48:24 +0200 [thread overview]
Message-ID: <20070731134824.6ec78447@frecb000686.frec.bull.fr> (raw)
In-Reply-To: <1185832234.3334.35.camel@josh-work.beaverton.ibm.com>
Hi Josh,
On Mon, 30 Jul 2007 14:50:34 -0700 Josh Triplett <josht@linux.vnet.ibm.com> wrote:
> On Tue, 2007-07-24 at 15:42 +0200, Sébastien Dugué wrote:
> > this one-liner fixes a bug in balance_rt_tasks() which sometimes manifests by
> > having a lower prio task being scheduled while a higher prio task is sitting
> > waiting on another runqueue.
> >
> > This is pretty hard to reproduce on low cpu count machines, for example, I
> > had to have sched_football run in a loop for ~38h before it failed on a dual HT
> > Xeon box.
>
> Very impressive find, and this does seem to improve things in some
> cases.
>
> However, with 2.6.22.1-rt8, which includes this patch, I still managed
> to get some failures after a few hours on an 8-way (quad dual-core) box.
> Preliminary results so far:
> 420 Final ball position: 0
> 2 Final ball position: 1
>
Darn, I thought it was it :(
I had a ~60h run on my box with the very same kernel without a single
failure.
Do you have any other user RT load running when those failures pop up?
Anyway, back to scheduler code dissection now.
Sébastien.
next prev parent reply other threads:[~2007-07-31 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 13:42 Sébastien Dugué
2007-07-25 7:27 ` Ingo Molnar
2007-07-30 21:50 ` Josh Triplett
2007-07-31 11:48 ` Sébastien Dugué [this message]
2007-08-01 0:18 ` Josh Triplett
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=20070731134824.6ec78447@frecb000686.frec.bull.fr \
--to=sebastien.dugue@bull.net \
--cc=dvhltc@us.ibm.com \
--cc=jean-pierre.dion@bull.net \
--cc=johnstul@us.ibm.com \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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
all inboxes | Powered by JetHome®