From: Rusty Russell <rusty@rustcorp.com.au>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Robust futexes
Date: Fri, 10 Mar 2006 10:17:48 +1100 [thread overview]
Message-ID: <1141946268.12863.79.camel@localhost.localdomain> (raw)
In-Reply-To: <43F5F87E.4030307@us.ibm.com>
On Fri, 2006-02-17 at 08:23 -0800, Darren Hart wrote:
> Rusty Russell wrote:
> telling the kernel that the lock is the tid allows the
> > kernel to do prio inheritence etc. in future.
>
> Priority Inheritance has come up a couple of times in relation to Ingo's new
> LightWeight Robust Futexes. Ingo has said that PI is orthogonal to LWRF, but I
> don't think we've heard if there are plans already in the works (or in his head
> :-) for PI. Rusty's comment above reads as "the current LWRF implementation
> cannot support PI" - is there something about it that makes PI impractical to
> implement?
Hi Darren!
Ingo's approach is indeed orthogonal. But the obvious approach to PI
etc is to tell the kernel who is holding the lock, by making the lock
value == TID of the holder. If we are heading towards this anyway, the
kernel could use this to implement robust mutexes, too, although not
with a 100% guarantee (due to tid wrap). Ingo doesn't like that,
though.
Hope that clarifies!
Rusty.
--
ccontrol: http://ozlabs.org/~rusty/ccontrol
prev parent reply other threads:[~2006-03-10 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 4:57 Rusty Russell
2006-02-17 6:42 ` Paul Jackson
2006-02-17 7:12 ` Rusty Russell
2006-02-17 7:29 ` Paul Jackson
2006-02-17 9:13 ` Ingo Molnar
2006-02-18 3:53 ` Rusty Russell
2006-02-19 4:11 ` Paul Jackson
2006-02-20 9:06 ` Ingo Molnar
2006-02-20 22:33 ` Paul Jackson
2006-02-17 15:47 ` Daniel Walker
2006-02-17 16:23 ` Darren Hart
2006-03-09 23:17 ` Rusty Russell [this message]
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=1141946268.12863.79.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome