From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Robust futexes
Date: Fri, 17 Feb 2006 15:57:51 +1100 [thread overview]
Message-ID: <1140152271.25078.42.camel@localhost.localdomain> (raw)
Hi Ingo, all,
Noticed (via LWN, hence the delay) your robust futex work. Have you
considered the less-perfect, but simpler option of simply having futex
calls which tell the kernel that the u32 value is in fact the holder's
TID?
In this case, you don't get perfect robustness when TID wrap occurs:
the kernel won't know that the lock holder is dead. However, it's
simple, and telling the kernel that the lock is the tid allows the
kernel to do prio inheritence etc. in future.
Cheers!
Rusty.
--
ccontrol: http://ozlabs.org/~rusty/ccontrol
next reply other threads:[~2006-02-17 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 4:57 Rusty Russell [this message]
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
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=1140152271.25078.42.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®