From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] new system calls - semacquire, semrelease
Date: Sun, 26 Mar 2006 03:04:52 +1100 [thread overview]
Message-ID: <775b8d190603250804l45b2c25ag865617b928ca0ab5@mail.gmail.com> (raw)
In-Reply-To: <db0621f360f1c7f04c84e4aa5cf63f4c@terzarima.net>
indeed al this stuff can be one with channels but locks are
often easier, paryicularly if nested.
newlock: fn(): ref Lock;
lock: fn(l: ref Lock);
rlock: fn(l: ref Lock);
canlock: fn(l: ref Lock): int;
canrlock: fn(l: ref Lock): int;
unlock: fn(l: ref Lock);
brucee
On 3/25/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> 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.
>
>
>
> ---------- Forwarded message ----------
> From: William Josephson <jkw@eecs.harvard.edu>
> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
> Date: Fri, 24 Mar 2006 23:50:45 -0500
> Subject: Re: [9fans] new system calls - semacquire, semrelease
> 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.
>
>
next prev parent reply other threads:[~2006-03-25 16:04 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
2006-03-25 16:04 ` Bruce Ellis [this message]
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=775b8d190603250804l45b2c25ag865617b928ca0ab5@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).