From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rwlocks on plan9
Date: Thu, 22 Sep 2011 12:46:02 +0100 [thread overview]
Message-ID: <22adeba8a2e8a2167f3ea4178f936085@terzarima.net> (raw)
In-Reply-To: <d4dae137a381e610157b08c0221df288@quintile.net>
>is this how its susposed to work?
yes. the queued locks are associated with data, not with a process:
one process can acquire the lock and another release it.
that probably isn't used often at all, but it's the best way to think of it.
spin locks have a tighter link with a process because (after all)
they're intended for short sections of code without rescheduling.
next prev parent reply other threads:[~2011-09-22 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 11:22 Steve Simon
2011-09-22 11:42 ` Sape Mullender
2011-09-22 11:46 ` Charles Forsyth [this message]
2011-09-22 19:33 Steve Simon
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=22adeba8a2e8a2167f3ea4178f936085@terzarima.net \
--to=forsyth@terzarima.net \
--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).