From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <55fbc9b0ce416859947f27410c05b5d1@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the backporting continues - /. stories maybe of interest
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
In-Reply-To: <3ED3516F.90203@proweb.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 28 May 2003 08:57:13 +0100
Topicbox-Message-UUID: b9ef02da-eacb-11e9-9e20-41e7f4b1d025

`backporting'?  have you seen what they do?
in Plan 9 (and from the same stock, early Inferno),
the single stack was at an intermediate stage described by
some data structures rooted in a single instance of the Fs structure.
having more than one stack required allocating an Fs per stack, and
changing functions to accept Fs* where needed.  a bit tedious but
otherwise fairly obvious and straightforward.  user-level programs
weren't much affected because you can bind what you like on /net and
if it's somewhere else the dial string names it.  you couldn't
honestly get a paper out of it.

what they did in the approach in the /.  article is an interesting
application of brute force: if you replicate
the kernel environment (including user processes) you might well
replicate the IP stack but it's almost a side effect.
(i'm sure there's at least one paper in it.  there's certainly at least one lesson.)
i wonder if i can link my virtual card punch to a virtual card reader
to do e-mail...