From: Sven-Thorsten Dietrich <sdietrich@mvista.com>
To: Ingo Molnar <mingo@elte.hu>, joe.korty@ccur.com
Cc: Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, inaky.perez-gonzalez@intel.com,
Steven Rostedt <rostedt@goodmis.org>,
Esben Nielsen <simlo@phys.au.dk>
Subject: Re: [PATCH] Priority Lists for the RT mutex
Date: Fri, 08 Apr 2005 01:05:03 -0700 [thread overview]
Message-ID: <1112947503.7093.28.camel@sdietrich-xp.vilm.net> (raw)
In-Reply-To: <20050408062811.GA19204@elte.hu>
On Fri, 2005-04-08 at 08:28 +0200, Ingo Molnar wrote:
> * Daniel Walker <dwalker@mvista.com> wrote:
>
> > This patch adds the priority list data structure from Inaky
> > Perez-Gonzalez to the Preempt Real-Time mutex.
>
> this one looks really clean.
>
> it makes me wonder, what is the current status of fusyn's? Such a light
> datastructure would be much more mergeable upstream than the former
> 100-queues approach.
Ingo,
Joe Korty has been doing a lot of work on Fusyn recently.
Fusyn is now a generic implementation, similar to the RT mutex. SMP
scalability is somewhat better for decoupled locks on PI (last I
checked). It has the extra bulk required to support user space.
The major issue that concerns the Fusym and the real-time patch is that
merging the kernel portion of Fusyn creates a collision of redundant PI
implementations with respect to the RT mutex.
The issues are outlined here:
http://developer.osdl.org/dev/mutexes/
There are a few mistakes on the page, (RT mutex does not do priority
ceiling), but for the most part the info is current.
If the RT mutex could be exposed in non PREEMPT_RT configurations,
the fulock portion could be superseded by the RT mutex, and the
remaining pieces merged in. Or vice versa.
We discussed the scenarios recently, any guidance you can offer to help
us out would be greatly appreciated.
http://lists.osdl.org/pipermail/robustmutexes/2005-April/000532.html
Sven
next prev parent reply other threads:[~2005-04-08 8:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:52 Daniel Walker
2005-04-08 6:28 ` Ingo Molnar
2005-04-08 8:05 ` Sven-Thorsten Dietrich [this message]
2005-04-10 11:09 ` Ingo Molnar
2005-04-12 17:56 ` Daniel Walker
2005-04-08 17:11 ` Daniel Walker
2005-04-10 10:53 ` Ingo Molnar
2005-04-11 16:19 ` Daniel Walker
2005-04-12 18:37 ` Paul E. McKenney
2005-04-08 21:25 Perez-Gonzalez, Inaky
2005-04-08 22:53 ` Daniel Walker
2005-04-08 23:05 Perez-Gonzalez, Inaky
2005-04-11 8:27 Perez-Gonzalez, Inaky
2005-04-11 8:42 ` Ingo Molnar
2005-04-11 8:49 Perez-Gonzalez, Inaky
2005-04-11 8:57 ` Ingo Molnar
2005-04-11 22:17 ` Bill Huey
2005-04-12 20:35 ` Esben Nielsen
2005-04-11 9:03 Perez-Gonzalez, Inaky
2005-04-11 22:31 Perez-Gonzalez, Inaky
2005-04-11 23:11 ` Bill Huey
2005-04-11 23:28 Perez-Gonzalez, Inaky
2005-04-12 0:27 ` Bill Huey
2005-04-12 0:36 Perez-Gonzalez, Inaky
2005-05-06 9:05 Oleg Nesterov
2005-05-06 11:13 ` Oleg Nesterov
2005-05-06 18:56 ` Daniel Walker
2005-05-06 18:13 Perez-Gonzalez, Inaky
2005-05-07 7:25 ` Oleg Nesterov
2005-05-09 7:30 ` Ingo Molnar
2005-05-09 8:08 ` Oleg Nesterov
2005-05-09 9:11 ` Ingo Molnar
2005-05-09 14:32 ` Oleg Nesterov
2005-05-09 18:13 ` Daniel Walker
2005-05-09 19:21 ` Steven Rostedt
2005-05-09 21:29 ` Daniel Walker
2005-05-09 22:15 ` Daniel Walker
2005-05-09 14:07 ` 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=1112947503.7093.28.camel@sdietrich-xp.vilm.net \
--to=sdietrich@mvista.com \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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®