From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 06:14:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5771916A4CF for ; Tue, 2 Mar 2004 06:14:08 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89B8F43D31 for ; Tue, 2 Mar 2004 06:14:07 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 41501 invoked from network); 2 Mar 2004 14:14:06 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:14:06 -0000 Message-ID: <404496AE.300E1457@freebsd.org> Date: Tue, 02 Mar 2004 15:14:06 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Wes Peters cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 14:14:08 -0000 Bruce M Simpson wrote: > > On Mon, Mar 01, 2004 at 10:16:25PM -0500, James wrote: > > > > [] move IPv4 routing to its own optimized routing table structure and > > > > finally it's about time :) > > I've been fielding suggestions from individuals who feel using a multi-bit > trie might be more suitable for achieving higher PPS rates. Yes. Which one should not matter. I want to make an API for the IPv4 routing code. Different routing implementations then can be loaded or changed at runtime or boot time. > > > > add multi-path and policy-routing options. (planned) > > > > would the policy-routing optioned table sort of similar to VRF's or > > different routing instances that could potentially be tied to userlands > > like Quagga? > > That's the plan, I believe, anyway... It would be nice if Quagga could be > taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. What is the relationship tcp-md5 --> policy-routing? -- Andre