From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Semaphores for libc Lock?
Date: Sat, 27 Mar 2010 21:52:22 -0300 [thread overview]
Message-ID: <32d987d51003271752u52f51962x2edd9912641bd96c@mail.gmail.com> (raw)
In-Reply-To: <f75780241003271740t4f0dad99i13c1497b26bcf474@mail.gmail.com>
http://plan9.bell-labs.com/magic/man2html/2/semacquire
On Sat, Mar 27, 2010 at 9:40 PM, Venkatesh Srinivas <me@acm.jhu.edu> wrote:
> Hi,
> In Russ Cox's and Sape Mullender's 2008 IWP9 paper on semaphores in Plan 9,
> they suggest that semaphore (semacquire/semrelease)-based locks in libc were
> better than the current spinning ones; they note that the locks would be
> replaced in the distribution soon.
> Is that still in the cards?
> -- vs
>
--
Federico G. Benavento
next prev parent reply other threads:[~2010-03-28 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 0:40 Venkatesh Srinivas
2010-03-28 0:52 ` Federico G. Benavento [this message]
2010-03-28 0:56 ` Venkatesh Srinivas
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=32d987d51003271752u52f51962x2edd9912641bd96c@mail.gmail.com \
--to=benavento@gmail.com \
--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).