From: Hubertus Franke <frankeh@watson.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Cc: lse-tech@lists.sourceforge.net
Subject: Re: furwocks: Fast Userspace Read/Write Locks
Date: Thu, 7 Mar 2002 10:28:34 -0500 [thread overview]
Message-ID: <20020307152730.2BD483FE06@smtp.linux.ibm.com> (raw)
In-Reply-To: <E16iwkE-000216-00@wagner.rustcorp.com.au>
In-Reply-To: <E16iwkE-000216-00@wagner.rustcorp.com.au>
On Thursday 07 March 2002 07:11 am, Rusty Russell wrote:
> This is a userspace implementation of rwlocks on top of futexes.
>
> Release was delayed because tdbtorture started crashing... turns out
> it's unrelated 2.5.6-pre2 wierdness (after a good 6 hours debugging
> <SIGH>).
>
> So I don't have numbers, but I'm pretty sure this is as good as it
> gets without explicit kernel support for rwlocks. Kudos to Paul
> Mackerras for the brainwork on this one. Blame me for the name.
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/futex-1.2.tar.gz
>
> Cheers!
> Rusty.
I'll integrate these into the ulockflex and see what the numbers are
and whether the implementation is correct.
--
-- Hubertus Franke (frankeh@watson.ibm.com)
prev parent reply other threads:[~2002-03-07 15:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 12:11 furwocks: Fast Userspace Read/Write Locks Rusty Russell
2002-03-07 12:40 ` Peter Wächtler
2002-03-07 14:41 ` Hubertus Franke
2002-03-07 12:50 ` Arjan van de Ven
2002-03-07 15:33 ` Hubertus Franke
2002-03-07 15:42 ` Arjan van de Ven
2002-03-07 19:11 ` Hubertus Franke
2002-03-07 20:17 ` H. Peter Anvin
2002-03-08 6:27 ` Rusty Russell
2002-03-08 6:29 ` H. Peter Anvin
2002-03-08 7:09 ` Rusty Russell
2002-03-08 19:32 ` Jamie Lokier
2002-03-08 1:22 ` Rusty Russell
2002-03-08 3:26 ` H. Peter Anvin
2002-03-08 9:21 ` Peter Wächtler
2002-03-08 18:13 ` Hubertus Franke
2002-03-09 4:50 ` Rusty Russell
2002-03-11 18:47 ` Hubertus Franke
2002-03-07 15:28 ` Hubertus Franke [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=20020307152730.2BD483FE06@smtp.linux.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=rusty@rustcorp.com.au \
/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.