Hyperstone (RISC/DSP) port .. TCP/IP?
Lex Spoon
lex at cc.gatech.edu
Tue Feb 27 03:08:37 UTC 2001
Tom Poliquin <poliquin at softcomp.com> wrote:
> > There would still be a load of integration work to do, not least ripping the
> > kernel dependencies out of that code, but at least you wouldn't have to
> > worry as much about fixing the stack in the face of bug reports --- like the
> > recent CERT advisory describing DoS attacks on a couple of the TCP states.
>
> I did consider the BSD stack (it's the subject of the entire TCP/IP Vol
> II) but
> you came up with the same objection that I did .. extracting the kernal
> 'stuff'
> looked daunting .. I also reviewed the Linux stack code commentary book
> in
> which that extraction looked even worse .. Your comment will send me
> back
> to review it one more time ..
>
>
Last I checked, "slirp" claimed to be using the BSD stack to handle its
TCP/IP. And "slirp" doesn't just *use* TCP/IP, and does strange things
to it as it passes by. So you might glance through slirp and see how
they managed the extraction.
-Lex
More information about the Squeak-dev
mailing list
|