From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: PI patch against 2.6.16-rt9
Date: Tue, 28 Mar 2006 23:02:48 +0200 [thread overview]
Message-ID: <20060328210248.GE1217@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603280002430.25351-100000@lifa03.phys.au.dk>
* Esben Nielsen <simlo@phys.au.dk> wrote:
> My girl friend will be angry for me not being to bed yet, but I had to
> steal time to make this patch. I hope I managed to send it without
> white-space damage or anything like it.
thanks - this looks fine to me, but i'm still worried about the
nonatomic chain boosting side-effects that i outlined in the previous
mail.
the tempting property of your patch is the fundamental reschedulability
of the boosting itself - and the resulting simplicity of locking. On the
con side, i dont see how we can detect deadlocks reliably, nor how we
can avoid 'incorrect boosting' (outlined in the previous mail), if the
chain gets 'broken'.
Ingo
next prev parent reply other threads:[~2006-03-28 21:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 23:42 PI patch against 2.6.16-rt9 Esben Nielsen
2006-03-26 23:47 ` Ingo Molnar
2006-03-27 0:07 ` Esben Nielsen
2006-03-27 0:11 ` Esben Nielsen
2006-03-27 0:21 ` Ingo Molnar
2006-03-27 15:00 ` Esben Nielsen
2006-03-27 23:05 ` Esben Nielsen
2006-03-28 21:02 ` Ingo Molnar [this message]
2006-03-28 20:55 ` Ingo Molnar
2006-03-28 21:17 ` Esben Nielsen
2006-03-28 21:24 ` Ingo Molnar
2006-03-28 22:51 ` Esben Nielsen
2006-03-29 7:14 ` Ingo Molnar
2006-03-29 7:59 ` Esben Nielsen
2006-03-29 12:35 ` Ingo Molnar
2006-03-28 21:36 ` Thomas Gleixner
2006-03-28 22:23 ` Esben Nielsen
2006-03-28 22:42 ` Thomas Gleixner
2006-03-28 23:34 ` Esben Nielsen
2006-03-28 23:59 ` Thomas Gleixner
2006-03-29 12:29 ` Ingo Molnar
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=20060328210248.GE1217@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=simlo@phys.au.dk \
--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