From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fun with rfork
Date: Sat, 1 Nov 2003 10:03:46 +0000 [thread overview]
Message-ID: <b06370a3dd4706e0ec2f9c10b461d881@caldo.demon.co.uk> (raw)
In-Reply-To: <012b01c3a007$e44099c0$8201a8c0@cc77109e>
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
even more than that!
i ought to have said that it's perhaps most interesting on
an x86. (Hint: how and where could you call rendezvous?)
[-- Attachment #2: Type: message/rfc822, Size: 2383 bytes --]
From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] fun with rfork
Date: Sat, 1 Nov 2003 10:35:53 +1100
Message-ID: <012b01c3a007$e44099c0$8201a8c0@cc77109e>
the spinptr code was replaced quite a while ago because it
just doesn't work. a rendezvous replaced it.
next prev parent reply other threads:[~2003-11-01 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 10:25 C H Forsyth
2003-10-31 23:35 ` Bruce Ellis
2003-11-01 10:03 ` Charles Forsyth [this message]
2003-11-01 11:40 ` Bruce Ellis
2003-11-01 12:41 ` 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=b06370a3dd4706e0ec2f9c10b461d881@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).