From owner-freebsd-isp Fri Oct 24 07:24:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA22560 for isp-outgoing; Fri, 24 Oct 1997 07:24:22 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA22554 for ; Fri, 24 Oct 1997 07:24:19 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [204.141.95.138]) by etinc.com (8.8.3/8.6.9) with SMTP id KAA18012; Fri, 24 Oct 1997 10:32:21 -0400 (EDT) Message-Id: <3.0.32.19971024102522.009f0e20@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 24 Oct 1997 10:25:23 -0400 To: Jim Shankland From: dennis Subject: Re: Routing thru a FreeBSD? Cc: isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:59 PM 10/23/97 -0700, you wrote: >> exhausting the PCI bandwidth is very much >> an issue that's not going to go away with a faster CPU. > >Definitely. Of course, sooner or later, we'll have PCI-UW or something. This is kind of like tackling the question of whether you can travel at faster than the speed of light, because currently CPUs arent capable of processing more than PCI can deliver. The bus transfer is not the limiting factor in your packets/second equation...it is a tiny piece (unlike the old days) and insignificant compared to software. Dennis > >Jim Shankland >Flying Fox Computer Systems, Inc. > >