From: Rusty Russell <rusty@rustcorp.com.au>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, matthew@hairy.beasts.org,
bcrl@redhat.com, david@mysql.com, wli@holomorphy.com,
linux-kernel@vger.kernel.org,
Hubertus Franke <frankeh@watson.ibm.com>
Subject: Re: [PATCH] Fast Userspace Mutexes III.
Date: Tue, 05 Mar 2002 12:34:29 +1100 [thread overview]
Message-ID: <E16i3qX-0005H3-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "04 Mar 2002 14:49:51 CDT." <1015271393.15277.112.camel@phantasy>
In message <1015271393.15277.112.camel@phantasy> you write:
> > +static spinlock_t futex_lock = SPIN_LOCK_UNLOCKED;
>
> Could we make this per-waitqueue?
Yes, once someone gives benchmarks proving it's worth doing the whole
"multiple locks and cache aligned" thing. Until then, it's premature
optimization.
> We should do:
>
> #define FUTEX_UP 1
> #define FUTEX_DOWN -1
Ack. Definitely.
> here. The preempt statements compile away if CONFIG_PREEMPT is not set,
> so you can just put them in, even on arches that don't do preemption
> yet.
Oops, that code shouldn't have been in patch, and the only reason that
preempt_disable() was commented out is that I tested the patch on 2.4.
> ... oh, and I would love an example of using it in userspace ;)
I'll throw it in for patch IV. 8)
> Nice work, Rusty.
I don't know if I can accept the kudos: it's now hovering at about 70%
my code, but only 20% my ideas.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-03-05 1:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 3:55 Rusty Russell
2002-03-04 19:49 ` Robert Love
2002-03-04 20:13 ` Davide Libenzi
2002-03-04 20:20 ` Matthew Kirkwood
2002-03-04 20:48 ` Hubertus Franke
2002-03-04 22:15 ` Davide Libenzi
2002-03-05 1:50 ` Robert Love
2002-03-05 2:53 ` Davide Libenzi
2002-03-05 3:45 ` Rusty Russell
2002-03-05 3:55 ` Davide Libenzi
2002-03-05 6:11 ` Rusty Russell
2002-03-05 17:23 ` Davide Libenzi
2002-03-05 15:09 ` Hubertus Franke
2002-03-05 4:30 ` Edgar Toernig
2002-03-07 1:58 ` Richard Henderson
2002-03-07 2:10 ` Davide Libenzi
2002-03-05 4:48 ` Rusty Russell
2002-03-05 15:15 ` Hubertus Franke
2002-03-06 1:31 ` Rusty Russell
2002-03-05 1:34 ` Rusty Russell [this message]
2002-03-07 1:52 ` Richard Henderson
2002-03-07 3:39 ` Rusty Russell
2002-03-07 8:48 ` Richard Henderson
2002-03-07 9: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=E16i3qX-0005H3-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bcrl@redhat.com \
--cc=david@mysql.com \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@hairy.beasts.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.com \
/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®