From: Daniel Walker <dwalker@mvista.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Esben Nielsen <simlo@phys.au.dk>,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: RE: FUSYN and RT
Date: 12 Apr 2005 15:33:19 -0700 [thread overview]
Message-ID: <1113345199.6389.30.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <F989B1573A3A644BAB3920FBECA4D25A02FD4673@orsmsx407>
On Tue, 2005-04-12 at 15:26, Perez-Gonzalez, Inaky wrote:
> You should not need any of this if your user space mutexes are a
> wrapper over the kernel space ones. The kernel handles everything
> the same and there is no need to take care of any special cases or
> variations [other than the ones imposed by the wrapping].
The problem situation that I'm thinking of is when a task gets priority
boosted by Fusyn , then gets priority boosted by an RT Mutex. In that
situation, when the RT mutex demotes back to task->static_prio it will
be lower than the priority that Fusyn has given the task (potentially).
I don't think that's handled in the kernel anyplace, is it?
Daniel
next prev parent reply other threads:[~2005-04-12 22:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 22:26 FUSYN and RT Perez-Gonzalez, Inaky
2005-04-12 22:33 ` Daniel Walker [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 23:36 Perez-Gonzalez, Inaky
2005-04-12 23:09 Perez-Gonzalez, Inaky
2005-04-12 21:28 Perez-Gonzalez, Inaky
2005-04-12 20:35 Perez-Gonzalez, Inaky
2005-04-12 23:11 ` Esben Nielsen
2005-04-13 0:27 ` Daniel Walker
2005-04-13 15:46 ` Steven Rostedt
2005-04-13 17:33 ` Daniel Walker
2005-04-13 18:38 ` Steven Rostedt
2005-04-15 22:51 ` Bill Huey
2005-04-15 23:37 ` Inaky Perez-Gonzalez
2005-04-16 1:14 ` Steven Rostedt
2005-04-16 1:20 ` Inaky Perez-Gonzalez
2005-04-16 1:38 ` Steven Rostedt
2005-04-16 1:53 ` Inaky Perez-Gonzalez
2005-04-16 2:31 ` Steven Rostedt
2005-04-16 3:00 ` Sven Dietrich
2005-04-16 3:31 ` Steven Rostedt
2005-04-16 13:05 ` john cooper
2005-04-16 14:23 ` Steven Rostedt
2005-04-16 14:51 ` john cooper
2005-04-16 4:05 ` Inaky Perez-Gonzalez
2005-04-18 5:30 ` Bill Huey
2005-04-18 7:37 ` Sven-Thorsten Dietrich
2005-04-18 11:33 ` Steven Rostedt
2005-04-12 19:35 Perez-Gonzalez, Inaky
2005-04-12 18:15 Daniel Walker
2005-04-12 20:29 ` Esben Nielsen
2005-04-12 22:15 ` Daniel Walker
2005-04-12 20:33 ` Joe Korty
2005-04-12 21:25 ` Daniel Walker
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=1113345199.6389.30.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=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