From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] stack reclamation on Unix using clone, rfork_thread, etc.
Date: Fri, 4 Jun 2004 21:02:24 +0200 [thread overview]
Message-ID: <035001c44a66$7b29e7c0$637f7d50@SOMA> (raw)
In-Reply-To: <6.1.1.1.0.20040604175442.021d8420@pop.free.fr>
> Ok. What do you think then about the following pseudo-code:
roll on lunix ...
next prev parent reply other threads:[~2004-06-04 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 15:33 Richard C Bilson
2004-06-04 15:53 ` Russ Cox
2004-06-04 18:43 ` boyd, rounin
2004-06-04 16:22 ` Philippe Anel
2004-06-04 16:24 ` Philippe Anel
2004-06-04 16:38 ` Russ Cox
2004-06-04 16:43 ` Charles Forsyth
2004-06-04 19:02 ` boyd, rounin [this message]
2004-06-04 18:35 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 16:44 Richard C Bilson
2004-06-04 14:39 Russ Cox
2004-06-04 15:20 ` Philippe Anel
2004-06-04 15:23 ` Philippe Anel
2004-06-04 18:30 ` boyd, rounin
2004-06-04 18:38 ` Russ Cox
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='035001c44a66$7b29e7c0$637f7d50@SOMA' \
--to=boyd@insultant.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).