On 21 Mar 2006, at 02:03, Darren Reed wrote:
If you were to design TCP/IP for Solaris today, where would you start andhow would you go about it? Assume as a set of base requirements that you: * have to support DLPI * have to support the BSD socket API * need to achieve high performance * handle hardware replacements/failures without a reboot * have to support IPsec, TCP, UDP, ICMP, IPv6, etc * have to support tunnelling in software * have to support link aggregation in software ...others...? Would you start with a STREAMS implementation and adapt that for other scenarious?
Given experience, certianly not.
Would you start with a non-STREAMS based implementation and try to fit a STREAMS/DLPI interface to it?
For legacy applications, probably. I would emulate DLPI on top of a native non-streams interface.
With respect to network interface drivers, would you change the way in which they interact with IP (as DLPI drivers) as the default mechanism?
That was one of the long term aims of Nemo.
Would you require that network interfaces expose additional interfaces that make it easier for developing layered network interfaces?
A h/w driver should be able to expose all the capabilities of the h/w to which it is bound. This too was an aim of Nemo.
Paul Durrant www.linkedin.com/in/pdurrant
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ networking-discuss mailing list [email protected]
