From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] semaphores
Date: Wed, 16 Jan 2002 07:48:58 +0000 [thread overview]
Message-ID: <20020116183511.AE27F19A08@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 39 bytes --]
As does the Lock module in Inferno.
[-- Attachment #2: Type: message/rfc822, Size: 1435 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] semaphores
Date: Tue, 15 Jan 2002 22:54:56 -0500
Message-ID: <20020116035456.13985.qmail@g.bio.cse.psu.edu>
A previous edition's malloc used a pipe with a byte in it as a semaphore.
I thought that was a lovely solution, given shared file descriptors.
next reply other threads:[~2002-01-16 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 7:48 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-22 23:05 [9fans] Semaphores Joel Salomon
2006-10-22 23:21 ` Russ Cox
2006-10-22 23:29 ` Steve Simon
2002-01-25 14:53 [9fans] semaphores Russ Cox
[not found] <rsc@plan9.bell-labs.com>
2002-01-16 3:44 ` Russ Cox
2002-01-16 3:54 ` Scott Schwartz
2002-01-16 11:14 ` Boyd Roberts
2002-01-16 15:47 ` Ronald G Minnich
2002-01-25 10:30 ` Ralph Corderoy
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=20020116183511.AE27F19A08@mail.cse.psu.edu \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
/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).