From owner-freebsd-net Mon Jul 2 13:40:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from pltn13.pbi.net (mta8.pltn13.pbi.net [64.164.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 36FFF37B406 for ; Mon, 2 Jul 2001 13:40:15 -0700 (PDT) (envelope-from hsu@FreeBSD.org) Received: from FreeBSD.org ([63.193.112.125]) by mta8.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GFV00LBS5EXRH@mta8.pltn13.pbi.net> for freebsd-net@freebsd.org; Mon, 02 Jul 2001 13:40:09 -0700 (PDT) Date: Mon, 02 Jul 2001 13:39:54 -0700 From: Jeffrey Hsu Subject: Re: fastforwarding? In-reply-to: "Your message of Mon, 02 Jul 2001 12:54:49 PDT." <200107021954.PAA25927@goliath.cnchost.com> To: Bakul Shah Cc: freebsd-net@freebsd.org Message-id: <0GFV00LBT5EXRH@mta8.pltn13.pbi.net> MIME-version: 1.0 X-Mailer: exmh version 2.1.1 10/15/1999 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > a stock freebsd system can't do more than 20K ~ 100K pkts/second due to > many bottlenecks I'd be interested in knowing where those bottlenecks were and fixing them. I currently hit the packets/sec limit running on gigabit ethernet cards, but so far I've been blaming it on the relatively old firm-ware based Tigon II NIC and not the BSD stack. > Even if it takes 0 ns to do a route lookup, So are you saying route lookup is not the bottleneck? > So *overall* you are better off using a trie algorithm. I'm thinking of the probability-shifted lc-trie algorithm described in http://klamath.stanford.edu/~pankaj/research.html Do you have a better algorithm in mind? Jeffrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message