From: Daniel Walker <dwalker@mvista.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, sdietrich@mvista.com,
Steven Rostedt <rostedt@goodmis.org>,
Esben Nielsen <simlo@phys.au.dk>
Subject: RE: [PATCH] Priority Lists for the RT mutex
Date: 08 Apr 2005 15:53:36 -0700 [thread overview]
Message-ID: <1113000816.26295.26.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <F989B1573A3A644BAB3920FBECA4D25A02F64643@orsmsx407>
On Fri, 2005-04-08 at 14:25, Perez-Gonzalez, Inaky wrote:
> I concur with Daniel. If we can decide how to deal with that (toss
> one out, keep one, merge them, whatever), we could reuse all the user
> space glue that is the hardest part to get right.
I have a preference to the Real-Time PI , but that's just cause I've
worked with it more. Ingo's really the one that should be make those
choices though, since he has the biggest influence over what goes into
sched.c ..
> Current tip of development has some issues with conditional variables
> and broadcasts (requeue stuff) that I need to sink my teeth in. Joe
> Korty is fixing up a lot of corner cases I wasn't catching, but
> other than that is doing fine.
You try to get out, and they suck you right back in.
> How long ago since you saw it? I also implemented the futex redirection
> stuff we discussed some months ago.
It's been a while since I've seen the fusyn scheduler changes. I have
the curernt fusyn CVS, I'll take a look at it.
Daniel
next prev parent reply other threads:[~2005-04-08 22:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 21:25 Perez-Gonzalez, Inaky
2005-04-08 22:53 ` Daniel Walker [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2005-05-06 9:05 Oleg Nesterov
2005-05-06 11:13 ` Oleg Nesterov
2005-05-06 18:56 ` Daniel Walker
2005-04-12 0:36 Perez-Gonzalez, Inaky
2005-04-11 23:28 Perez-Gonzalez, Inaky
2005-04-12 0:27 ` Bill Huey
2005-04-11 22:31 Perez-Gonzalez, Inaky
2005-04-11 23:11 ` Bill Huey
2005-04-11 9:03 Perez-Gonzalez, Inaky
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 8:27 Perez-Gonzalez, Inaky
2005-04-11 8:42 ` Ingo Molnar
2005-04-08 23:05 Perez-Gonzalez, Inaky
2005-04-07 17:52 Daniel Walker
2005-04-08 6:28 ` Ingo Molnar
2005-04-08 8:05 ` Sven-Thorsten Dietrich
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
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=1113000816.26295.26.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®