From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interesting timing tests
Date: Mon, 21 Jun 2010 12:42:26 -0400 [thread overview]
Message-ID: <AANLkTikuFZdW-YR8pyDgXQ05Ymvyq6kcSecGGE51q8ju@mail.gmail.com> (raw)
In-Reply-To: <a4c3e91d8044dc47b504fab2bf11aa54@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Mon, Jun 21, 2010 at 10:40 AM, erik quanstrom <quanstro@quanstro.net>wrote:
> void
> lock(ulong *l)
> {
> ulong old;
> ushort next, owner;
>
> old = _xadd(l, 1);
> for(;;){
> next = old;
> owner = old>>16;
> old = *l;
> if(next == owner)
> break;
> }
> }
>
> void
> unlock(ulong *l)
> {
> _xadd(l, 1<<16);
> }
Sure, that's reasonable in C; (i wasn't sure how to do it in asm for 8_a_,
that was what I was asking about). Just also remember to provide xadd; the
distribution 8a and 8l didn't support it last I checked.
Just another observation, we can bypass the load of old in the uncontended
case if we reverse old = *l and the compare/break in lock.
Anyway, thoughts on this lock?
-- vs
[-- Attachment #2: Type: text/html, Size: 1332 bytes --]
next prev parent reply other threads:[~2010-06-21 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 23:26 erik quanstrom
2010-06-19 13:42 ` Richard Miller
2010-06-20 1:36 ` erik quanstrom
2010-06-20 7:44 ` Richard Miller
2010-06-20 12:45 ` erik quanstrom
2010-06-20 16:51 ` Richard Miller
2010-06-20 21:55 ` erik quanstrom
2010-06-21 1:41 ` erik quanstrom
2010-06-21 3:46 ` Venkatesh Srinivas
2010-06-21 14:40 ` erik quanstrom
2010-06-21 16:42 ` Venkatesh Srinivas [this message]
2010-06-21 16:43 ` erik quanstrom
2010-06-21 21:11 ` Bakul Shah
2010-06-21 21:21 ` erik quanstrom
2010-06-21 21:47 ` Bakul Shah
2010-06-21 22:16 ` erik quanstrom
2010-06-22 3:24 ` Lawrence E. Bakst
2010-06-23 1:09 ` erik quanstrom
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=AANLkTikuFZdW-YR8pyDgXQ05Ymvyq6kcSecGGE51q8ju@mail.gmail.com \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).