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: Wed, 01 Jun 2005 16:58:37 -0700 [thread overview]
Message-ID: <1117670317.7646.11.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <Pine.OSF.4.05.10506011603560.1707-100000@da410.phys.au.dk>
On Wed, 2005-06-01 at 16:07 +0200, Esben Nielsen wrote:
>
> Do you plan to use that callback for priority inheritance?
> If so: It would lead to an recursive algorithm. That is not very nice in
> the kernel with a limited call-stack. It is not so much a problem if the
> mechanism is used in the kernel only, but if it is used for user-space
> locking, which can have unlimited neesting, it is potential problem.
There is an API for for priority inheritance, the call by is strictly
for the PI mechanism to signal when it changes a waiters priority , as
the result of PI.
It's somewhat explained in linux/pi.h . Currently the rt_mutex uses this
callback to move the waiter depending on it's new priority.
I'm not sure I see how this could become recursive, could you explain
more?
Daniel
next prev parent reply other threads:[~2005-06-02 0:01 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 [this message]
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
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=1117670317.7646.11.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®