From: Daniel Walker <dwalker@mvista.com>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, sdietrich@mvista.com,
rostedt@goodmis.org, inaky.perez-gonzalez@intel.com
Subject: Re: [PATCH] Abstracted Priority Inheritance for RT
Date: Thu, 02 Jun 2005 10:31:11 -0700 [thread overview]
Message-ID: <1117733471.20350.2.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <Pine.OSF.4.05.10506021713200.3853-100000@da410.phys.au.dk>
On Thu, 2005-06-02 at 17:18 +0200, Esben Nielsen wrote:
> Good :-)
> I asked the question because I considered (and started but didn't
> have time) doing what you have done. I wanted to generalise the rt_mutex
> to have real rw_lock as well - which was dropped due to the
> non-deterministc behavioir even with PI. To do that I needed to have the
> recursion and the callback..
I'm not planning to do a real rw-lock, but I hope this generic PI will
help with that. I'm still not completely satisfied with this callback
structure , but I don't see a better way to do it. Do you have an
suggestions for replacing it?
Daniel
next prev parent reply other threads:[~2005-06-02 17:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 2:57 Daniel Walker
2005-06-01 3:35 ` Steven Rostedt
2005-06-01 7:54 ` Ingo Molnar
2005-06-01 12:57 ` Daniel Walker
2005-06-01 14:07 ` Esben Nielsen
2005-06-01 23:58 ` Daniel Walker
2005-06-02 8:25 ` Esben Nielsen
2005-06-02 15:11 ` Daniel Walker
2005-06-02 15:18 ` Esben Nielsen
2005-06-02 17:31 ` Daniel Walker [this message]
2005-06-02 20:27 ` Esben Nielsen
2005-06-02 21:50 ` Daniel Walker
2005-06-03 9:08 ` Esben Nielsen
2005-06-02 0:10 Perez-Gonzalez, Inaky
2005-06-02 0:25 ` Daniel Walker
2005-06-02 0:52 linux
2005-06-02 1:21 Perez-Gonzalez, Inaky
2005-06-02 1:22 Perez-Gonzalez, Inaky
2005-06-02 5:43 ` john cooper
2005-06-03 0:54 ` Bill Huey
2005-06-03 1:10 ` Sven Dietrich
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=1117733471.20350.2.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sdietrich@mvista.com \
--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
all inboxes | Powered by JetHome®