From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] XaoS - first useable version
Date: Wed, 10 Sep 1997 18:11:59 +0100 [thread overview]
Message-ID: <19970910171159.un8g8hc8BsVtgYluDUz-i86cJD0se4mQDGA_ptfarT4@z> (raw)
when describing the process synchronisation primitives,
i forgot to mention rendezvous(2), which is the system
call to synchronise two processes. given rendezvous,
<lock.h>, and rfork, you should be able to write the little
you need fairly easily. processes can rendezvous to
collect points without busy waiting on the spin lock.
note that you should
rfork(RFNAMEG)
in main(), to ensure that you've got a separate space
for the rendezvous values. (why RFNAMEG? because that rendezvous
space is tied to the name space in Plan 9; in Brazil it
becomes a separate resource controlled by a distinct flag to rfork.)
next reply other threads:[~1997-09-10 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-10 17:11 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-12 8:07 Jan
1997-09-11 8:12 Jan
1997-09-11 8:09 Jan
1997-09-10 17:28 Scott
1997-09-10 9:19 Jan
1997-09-10 9:03 Jan
1997-09-10 7:42 forsyth
1997-09-10 7:06 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=19970910171159.un8g8hc8BsVtgYluDUz-i86cJD0se4mQDGA_ptfarT4@z \
--to=forsyth@caldo.demon.co.uk \
/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).