Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!rutgers!bellcore!messy!mo
From: mo@messy.bellcore.com (Michael O'Dell)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: desperately need an answer
Message-ID: <23961@bellcore.bellcore.com>
Date: 6 Jun 90 16:50:26 GMT
References: <9006061544.AA08499@ucbvax.Berkeley.EDU>
Sender: news@bellcore.bellcore.com
Reply-To: mo@messy.UUCP (Michael O'Dell)
Organization: Center for Chaotic Repeatabilty
Lines: 17

(1) the limitations aren't that severe because it turns out
implementing TCP/IP isn't as piggish as first thought.
Further, previous experience with putting NCP outside the kernel
for just the suggestes reasons was a cosmic lose in terms of
complexity.

but the important one is....

(2) SPEED!!!!! The last thing in the world you want is a few
extra context switches per packet and per network read/write.
Putting it ouside the kernel almost guarantees extra data copies
as well as the extra context switches.

So, aside from being gratuitously complex and hideously slow, the
idea is great.  

	-Mike