From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4e5523e47f12f4e050d4cb4ea69b46db@cat-v.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Van Jacobsen's network stack restructure
Date: Wed,  1 Feb 2006 18:46:29 +0100
From: uriel@cat-v.org
In-Reply-To: <e0ac85f90601312028w2b5d8ac3uc6ab5db0e2e3cea@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: ed9c75fe-ead0-11e9-9d60-3106f5b1d025

> anyone seen this?
> 
> http://www.lemis.com/grog/Documentation/vj/
Yes quite interesting, and here is a nice writeup: 
http://vger.kernel.org/~davem/cgi-bin/blog.cgi/2006/01/27
 
> i don't know if his methods have any application to Plan 9, since the
> Plan 9 IP stack doesn't seem to have the lineage of the linux and bsd
> stacks. i am not intimate with the IP stack code, but it might bear a
> lookover.
>>From the very little I know about our IP stack(which comes from reading Nemo's
excellent commentary on the 3rd edition kernel source), we might be not too
far from a design similar to what is described there, but I might be completely
wrong.

And even if it's not, /net makes it easy to put the IP stack in user space without
having to change a single line of application code. Ah, the more I deal with
Plan 9, the more I love it :)

Maybe we should try to convince those lunix people to replace sockets with
something like /net? ;)

uriel

> 
> it at least has me curious enough to go digging around through the code. :-)
>