From owner-freebsd-net  Fri Mar 16  9:32:39 2001
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 176ED37B719
	for <freebsd-net@FreeBSD.ORG>; Fri, 16 Mar 2001 09:32:35 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA60083;
	Fri, 16 Mar 2001 11:40:15 -0500 (EST)
	(envelope-from wollman)
Date: Fri, 16 Mar 2001 11:40:15 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200103161640.LAA60083@khavrinen.lcs.mit.edu>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: same interface Route Cache
In-Reply-To: <20010316110803.B12010@daemon.ninth-circle.org>
References: <Pine.BSF.4.21.0103092053290.13355-100000@cody.jharris.com>
	<20010316110803.B12010@daemon.ninth-circle.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Fri, 16 Mar 2001 11:08:03 +0100, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> said:

> Correct me if wrong, but if I recall BSD natively already held a route
> cache, although it might not be the best route cache which we could come
> up with.

It does, but there is only a single route cached there.  A better
implementation might have a small hash table (e.g., 16 entries), but
that could make things more complex when we decide to delete a route.

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message