From: Linh Dang <linhd@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH] FUSYN Realtime & robust mutexes for Linux, v2.3.1
Date: Thu, 05 Aug 2004 09:23:06 -0400 [thread overview]
Message-ID: <wn5llgtyb0l.fsf@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <1091704539.5031.42.camel@bach> (Rusty Russell's message of "Thu, 05 Aug 2004 21:48:05 +1000")
Rusty Russell <rusty@rustcorp.com.au> wrote:
> I don't think this is neccessarily true: I think that platforms with
> 64-bit compare-and-exchange can do the whole thing in userspace.
> They would set the mutex and stamp in the thread ID simultanously,
> allowing for "dead thread" detection (ie. I didn't get the lock, and
> it's a robust mutex: check the holder is still alive).
Or for priority-inheritance: try get the lock, if failed raised the
holder's priority to mine if necessary.
>
> W/o 64-bit compare-and-exchange a 100% robust solution may not be
> possible though.
PPC arch can do a lot of things in a pseudo-atomic way.
>
> Thoughts?
> Rusty.
--
Linh Dang
next prev parent reply other threads:[~2004-08-05 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 9:13 [RFC/PATCH] FUSYN Realtime & robust mutexes for Linux, v2.3.1 Perez-Gonzalez, Inaky
2004-08-05 6:21 ` Andrew Morton
2004-08-05 7:06 ` Ulrich Drepper
2004-08-05 7:17 ` Andrew Morton
2004-08-05 7:37 ` Ulrich Drepper
2004-08-05 7:40 ` Andrew Morton
2004-08-05 8:22 ` Ulrich Drepper
2004-08-05 10:42 ` Ingo Molnar
2004-08-05 11:48 ` Rusty Russell
2004-08-05 13:23 ` Linh Dang [this message]
2004-08-05 13:26 ` Linh Dang
2004-08-05 14:02 ` Chris Friesen
2004-08-05 10:34 ` Ingo Molnar
2004-08-05 10:59 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 8:39 Eric Valette
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:22 Perez-Gonzalez, Inaky
2004-08-05 18:37 Perez-Gonzalez, Inaky
2004-08-05 18:39 Perez-Gonzalez, Inaky
2004-08-05 18:39 Perez-Gonzalez, Inaky
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=wn5llgtyb0l.fsf@linhd-2.ca.nortel.com \
--to=linhd@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.