9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new system calls - semacquire, semrelease
Date: Sat, 25 Mar 2006 09:22:00 +0000	[thread overview]
Message-ID: <db0621f360f1c7f04c84e4aa5cf63f4c@terzarima.net> (raw)
In-Reply-To: <20060325045045.GA13159@mero.morphisms.net>

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

there is lock(2) in the public inferno distribution.  the implementation is amusing.
things like counting semaphores have been too, though not distributed,
but these things are not used as much as channels in Limbo programming.

[-- Attachment #2: Type: message/rfc822, Size: 3129 bytes --]

From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] new system calls - semacquire, semrelease
Date: Fri, 24 Mar 2006 23:50:45 -0500
Message-ID: <20060325045045.GA13159@mero.morphisms.net>

On Fri, Mar 24, 2006 at 11:52:38AM +1100, Bruce Ellis wrote:
> a bit like ...
>
> 	semnew:		fn(n: int): ref Sem;
> 	semacquire:	fn(s: ref Sem);
> 	semcanacq:	fn(s: ref Sem): int;
> 	semrelease:	fn(s: ref Sem);
>
> in ozinferno

Interesting...  Say, is ozinferno available?
Sounds like it might be interesting to poke at it.

  parent reply	other threads:[~2006-03-25  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  0:43 Russ Cox
2006-03-24  0:52 ` Bruce Ellis
2006-03-25  4:50   ` William Josephson
2006-03-25  6:46     ` Bruce Ellis
2006-03-25  9:22     ` Charles Forsyth [this message]
2006-03-25 16:04       ` Bruce Ellis
2006-03-25 16:12         ` Russ Cox
2006-03-26  7:27           ` Lyndon Nerenberg
2006-03-26 17:11             ` Bruce Ellis
2006-03-26 18:59               ` Charles Forsyth

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=db0621f360f1c7f04c84e4aa5cf63f4c@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).