From: "Taj Khattra" <taj.khattra@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Creating a custom jmp_buf; libthread implementation question
Date: Tue, 14 Nov 2006 11:44:48 -0800 [thread overview]
Message-ID: <57a21f730611141144h2c5e9ef8n370c9b0cf0ec4b81@mail.gmail.com> (raw)
In-Reply-To: <7871fcf50611140838u77edf6c5g1a3aeb6caa27f24b@mail.gmail.com>
> might want to also checkout Russ' libtask (at swtch.com).
another one is the implementation of the Thread, Sem and Chan
interfaces in dave hanson's cii
(http://www.cs.princeton.edu/software/cii/). chapter 20 has the gory
details.
next prev parent reply other threads:[~2006-11-14 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 3:23 Joel Salomon
2006-11-14 3:33 ` Joel Salomon
2006-11-14 9:39 ` Bruce Ellis
2006-11-14 12:34 ` Russ Cox
2006-11-14 16:15 ` Joel Salomon
2006-11-21 3:03 ` Joel Salomon
2006-11-21 3:03 ` William Josephson
2006-11-21 3:08 ` Russ Cox
2006-11-14 9:58 ` Gorka guardiola
2006-11-14 16:25 ` Joel Salomon
2006-11-14 16:38 ` Joel Salomon
2006-11-14 19:44 ` Taj Khattra [this message]
2006-11-14 5:44 ` [9fans] Skip Tavakkolian
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=57a21f730611141144h2c5e9ef8n370c9b0cf0ec4b81@mail.gmail.com \
--to=taj.khattra@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).