From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RT] bad BUG_ON in rtmutex.c
Date: Tue, 18 Apr 2006 15:52:49 +0200 [thread overview]
Message-ID: <20060418135249.GA14030@elte.hu> (raw)
In-Reply-To: <1145371913.5447.48.camel@localhost.localdomain>
* Daniel Walker <dwalker@mvista.com> wrote:
> > But, as PI matures, it seems to be more and more acceptable.
>
> I read an article on priority ceiling as another method of doing
> this. Priority ceiling doesn't seem better, but at the same time I
> can't imagine how you'd implement it in Linux, or not in a straight
> forward way .
it's already implemented and can be done in userspace: userspace can do
it by doing a sys_setscheduler() call when entering the critical
section, and another one when exiting it. (PI is obviously faster
because there the futex fastpath can be pure-userspace.)
Ingo
next prev parent reply other threads:[~2006-04-18 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 1:48 Steven Rostedt
2006-04-18 12:20 ` Daniel Walker
2006-04-18 12:34 ` Steven Rostedt
2006-04-18 13:11 ` Daniel Walker
2006-04-18 13:50 ` Steven Rostedt
2006-04-18 13:55 ` Steven Rostedt
2006-04-18 14:09 ` Daniel Walker
2006-04-18 14:32 ` Steven Rostedt
2006-04-18 14:51 ` Daniel Walker
2006-04-18 13:52 ` Ingo Molnar [this message]
2006-04-18 15:06 ` Steven Rostedt
2006-04-18 16:14 ` Daniel Walker
2006-04-18 16:24 ` Steven Rostedt
2006-04-18 14:13 ` [PATCH -rt] Remove false BUG_ON from rtmutex.c Steven Rostedt
2006-04-18 13:12 ` 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=20060418135249.GA14030@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®