> Date: Wed, 17 Jan 1996 17:10:30 -0700
> From: Chris Torek <torek@BSDI.COM>
> To: bwalker@musings.com, greywolf@captech.com,
>         greywolf@defender.VAS.viewlogic.com
> Subject: Re: Serial port issues on Sun4/260
> Cc: dgilbert@pci.on.ca, port-sparc@NetBSD.ORG
> 
> >Connect thru STREAMS is also less than optimal.  Pushing all the required
> >modules atop the STREAM head costs some time.
> 
> It *should* be unnoticeable.  The problem with SysV STREAMS, if you
> have ever looked at it, is that it bends the stream model (a simple
> up- and downward dataflow) all out of shape to accomodate:
> 
> 	- control messages (ioctl et al), with timeouts
> 	  (this simply does not fit in the model! I do not know
> 	  of any good way to do it)
> 	- multiplexors
> 
> The stream multiplexors in particular are super-hairy, quite literally
> thousands of lines of code to do what the IP protocol switch or the
> TCP control blocks do in hundreds.  There has got to be a better way.
> 


When I do something. And what I do has not been decided yet. But, you
are quite right. I have to look at the multiplexor code all the time
at work. And it's a mess.

In all honesty, I will most likely avoid doing multiplexors at first.
It's just too messy..

-brad w.