From: "William K. Josephson" <wkj@acm.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Cross-platform
Date: Tue, 2 Jan 2001 16:52:16 -0500 [thread overview]
Message-ID: <20010102165216.A22201@honk.eecs.harvard.edu> (raw)
In-Reply-To: <slrn952hln.7h4.randolph@panix3.panix.com>; from randolph@panix.com on Tue, Jan 02, 2001 at 05:51:09PM +0000
On Tue, Jan 02, 2001 at 05:51:09PM +0000, Randolph Fritz wrote:
> On Mon, 1 Jan 2001 19:33:05 GMT, Russ Cox <rsc@plan9.bell-labs.com> wrote:
> >
> >the scripts that do everything require
> >byron rakitzis's rc and the inferno mk,
> >but it'd be nice to do without them.
> >rfork(RFMEM) is the sticking point, if i
> >remember correctly.
> >
>
> Newer (2.2/libc2) Linux kernels support an __clone() system call,
> which could be used, so far as I can tell, to implement most of
> rfork(). Of course, one would also have to port any necessary
> synchronization primitives.
Yes. You can't get all of the rfork() semantics with __clone(2), of
course, but as I said, I've already implemented what you can get -- it
is a straightforward hack. The trouble is that the interface is a
kludge compared to fork as you'll need to futz with some inline
assembly to set up the stacks. Although to a lesser extent, the same
is true of FreeBSD rfork(RFMEM) as, contrary to the manual page, rfork
fails to split the stack. More annoying still, you have to do it for
each different Unix. The documentation for kernel threads for DU aka
OSF/1 was virtually non-existant on a number of sites I use, for
instance.
-WJ
next prev parent reply other threads:[~2001-01-02 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 19:07 Russ Cox
2001-01-01 21:53 ` William K. Josephson
2001-01-01 21:59 ` William K. Josephson
2001-01-02 17:51 ` Randolph Fritz
2001-01-02 21:52 ` William K. Josephson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-01 19:57 presotto
[not found] <200101011841.f01IfIf01104@cactus.bheadley.org>
2001-01-01 18:49 ` Bryan W. Headley
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=20010102165216.A22201@honk.eecs.harvard.edu \
--to=wkj@acm.org \
--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).