From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Esben Nielsen <simlo@phys.au.dk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc6-rt1
Date: Tue, 14 Mar 2006 23:22:17 +0100 [thread overview]
Message-ID: <1142374937.19916.665.camel@localhost.localdomain> (raw)
In-Reply-To: <20060314221111.GA7118@elte.hu>
On Tue, 2006-03-14 at 23:11 +0100, Ingo Molnar wrote:
> > > no. We have to run deadlock detection to avoid things like circular lock
> > > dependencies causing an infinite schedule+wakeup 'storm' during priority
> > > boosting. (like possible with your wakeup based method i think)
> > No, all tasks would just settle on the highest priority and then the
> > wakeups would stop.
>
> you are right, that shouldnt be possible. But how about other, SMP
> artifacts? What if the woken up task runs on another CPU, and the whole
> chain of boosting is thus delayed?
And it does not solve the problem of ad hoc deadlock detection at all.
tglx
next prev parent reply other threads:[~2006-03-14 22:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 22:02 2.6.16-rc6-rt1 Ingo Molnar
2006-03-12 23:17 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-12 23:36 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:43 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-13 9:25 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 13:49 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:56 ` [PATCH] 2.6.16-rc6-rt1: Fix redefinition and unknown symbol Jan Altenberg
2006-03-13 9:11 ` Ingo Molnar
2006-03-13 13:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-13 14:29 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 16:06 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 0:22 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 8:12 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 8:33 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 10:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:18 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:11 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:22 ` Thomas Gleixner [this message]
2006-03-15 11:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:28 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:58 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 20:40 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:00 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 1:54 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 7:51 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 2:22 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 8:00 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-15 16:25 ` 2.6.16-rc6-rt1 John Richard Moser
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=1142374937.19916.665.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=simlo@phys.au.dk \
/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