Date: Sat, 04 Jan 1997 15:44:54 -0800 From: Julian Elischer <julian@whistle.com> To: Darren Reed <avalon@coombs.anu.edu.au> Cc: Julian Elischer <julian@freefall.freebsd.org>, hackers@freefall.freebsd.org Subject: Re: New Networking framework for BSD Message-ID: <32CEEB76.237C228A@whistle.com> References: <199701042305.PAA21612@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Darren, see my mail drirectly to you... you appear to have commented without reading the doc yet.. I'm not trying to replace anything. Just make a framework for such services as frame relay and ATM, at the LINK level. I sent you a copy of the overview.. please read it, as I'd like your comments! Darren Reed wrote: > > I have one _big_ concern with this: > > Currently we have very well known and understood networking code inside the > kernel which has been around for years and has matured over that time to > become a very reliable backbone. Rewriting this (or replacing it) with new > code will effectively put FreeBSD back many years in so far as being sure > that it has reliable networking. Two excellent cases which show this are > Solaris 2 & Linux (both of which have their own TCP/IP stack as opposed to > BSD's) and amusingly the BSD socket interface is planned for Solaris 2.6 > for software performance reasons :) > > So, as long as we're prepared to have an "options TESTINET" (or similar) > for the kernel - which would be mutually exclusive with "options INET" - > for some years to come, it looks like an interesting idea worth pursuing. > > Darren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32CEEB76.237C228A>