From owner-freebsd-isp Thu Oct 23 17:13:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA08021 for isp-outgoing; Thu, 23 Oct 1997 17:13:43 -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 RAA08015 for ; Thu, 23 Oct 1997 17:13:40 -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 UAA13046; Thu, 23 Oct 1997 20:21:34 -0400 (EDT) Message-Id: <3.0.32.19971023201441.00ade850@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 23 Oct 1997 20:14:41 -0400 To: "IBS / Andre Oppermann" 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 12:41 AM 10/24/97 +0200, you wrote: >Tony Li wrote: >-snip- >> Ob FreeBSD: The point here is that at some point, when you need many >> hundreds of thousands of PPS of forwarding, normal processors just >> fail to >> provide the necessary speed. Note that for most situations, this is >> not >> necessary. A heavily hacked FreeBSD system can get around 100Kpps. >> Of >> course at this point, you also run out of PCI bandwidth, so you've >> maxed >> out the rest of the hardware too. Of course these numbers change linearly as Intel cranks out faster processors. Dennis