Date: Tue, 15 Dec 1998 16:11:29 -0800 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk>, "Jonathan M. Bresler" <jmb@FreeBSD.ORG> Cc: johan@granlund.nu, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! Message-ID: <199812160011.QAA00971@salsa.gv.tsc.tdk.com> In-Reply-To: Poul-Henning Kamp <phk@critter.freebsd.dk> "Re: if_sppp is BROKEN!!!" (Dec 15, 12:23am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 15, 12:23am, Poul-Henning Kamp wrote: } Subject: Re: if_sppp is BROKEN!!! } But with that said, there is still something to be said for modular } and well defined interfaces. But streams ? No. They were great } for async protocols, but they fail badly for packet stuff. This is one of my favorite quotes, from Van Jacobson in his cslip package: Note that in Sun OS 4.x, slip runs over a "streams" tty driver where much of the underlying support code was taken from AT&T's System-V Unix. This support code is incredibly bad: A Sun-3/50 will run both it's serial ports at 38,400 baud with no problems under Sun OS 3.x (which uses the Berkeley/V7 tty driver). That same 3/50 can not keep up with one serial port running at 9600 baud under Sun OS 4.0.3. The AT&T code also doesn't handle any kind of exception correctly: If it runs out of stream buffers or gets a signal or interrupt at the wrong time, the system will crash. So, run Sun OS 3 if you have any choice. If you have no choice, try this stuff but don't expect reasonable performance or robustness. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812160011.QAA00971>