From owner-freebsd-hackers Thu Oct 19 17:39:10 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA07508 for hackers-outgoing; Thu, 19 Oct 1995 17:39:10 -0700 Received: from etinc.com (etinc-gw.new-york.net [165.254.13.209]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA07498 for ; Thu, 19 Oct 1995 17:39:05 -0700 Received: from trumpet.etnet.com (trumpet.etnet.com [129.45.17.35]) by etinc.com (8.6.11/8.6.9) with SMTP id UAA29399; Thu, 19 Oct 1995 20:52:48 -0400 Date: Thu, 19 Oct 1995 20:52:48 -0400 Message-Id: <199510200052.UAA29399@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (dennis) Subject: Re: Bragging rights.. Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk Joe Greco says..... >Dennis started this thread on the assertion that his sync serial cards can >do very high speeds quite easily :-) Actually, Dennis started this thread by trying to get a price reference for the Async solution that Jordan referred to....I did not start it by saying that sync is better than async. My point was that if for about the same money you can have a more flexible solution that will use less of your CPU it is worth considering. Unlike most of you, my perspective is marketability....not necessarily your (wrong) opinion that async is just as good. If its not cheaper, which has always been the sole selling point for async, then it's a no-brainer. I have a 386DX/40 routing between a >T1 (1.544Mb/s) and an Ethernet and it handles average mixes of traffic >without any trouble (it runs into problems if you start saturating the T1 >with small packets however). It is QUITE impressive :-) I don't think >you'd need to do any crystal switches to do what you describe, since the >board is designed to be quite flexible. However, you are probably limited to >packet modes such as PPP (Dennis? I am extrapolating here, any solid >info? I was never able to access raw data streams, although I only looked >briefly) Its limited to whatever I wrote for it so far. There's not much market for raw data streams. We can run 2 dos boxes back to back at 4mbs and run all day. The overruns you're seeing with small packets is a FreeBSD/CPU power issue in processing IP packets, and can be linearly corrected by increasing CPU power...the capabilities are limited only by what unix can handle as the per packet latency is fairly high, particularly on a slow box. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25