From owner-freebsd-net@FreeBSD.ORG  Tue Nov 11 18:45:08 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6BA9A16A4CE
	for <freebsd-net@freebsd.org>; Tue, 11 Nov 2003 18:45:08 -0800 (PST)
Received: from web10007.mail.yahoo.com (web10007.mail.yahoo.com
	[216.136.130.43])
	by mx1.FreeBSD.org (Postfix) with SMTP id 7E69643F93
	for <freebsd-net@freebsd.org>; Tue, 11 Nov 2003 18:45:07 -0800 (PST)
	(envelope-from oldpopsong@yahoo.com)
Message-ID: <20031112024507.89398.qmail@web10007.mail.yahoo.com>
Received: from [218.244.38.34] by web10007.mail.yahoo.com via HTTP;
	Tue, 11 Nov 2003 18:45:07 PST
Date: Tue, 11 Nov 2003 18:45:07 -0800 (PST)
From: popsong old <oldpopsong@yahoo.com>
To: Andre Oppermann <oppermann@pipeline.ch>
In-Reply-To: <3FB0ADE8.44B00CF9@pipeline.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-net@freebsd.org
Subject: Re: tcp hostcache and ip fastforward for review
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Nov 2003 02:45:08 -0000

--- Andre Oppermann <oppermann@pipeline.ch> wrote:
> > BTW, we'll get even better performance if we keep both
> > interfaces' MAC addresses in cache (and call
> > ifp->if_start directly). This requires to keep
> > ethernet header in mbuf untouched and is only relevant
> > in ethernet though. I implemented such layer 2 cache
> > in a local version of IPFilter and got some good
> > results.
> 
> I don't understand why you want to do that unless you
> are doing bridging. We have to look up the mac address
> of the next hop anyway. If that is not already in the
> routing table it needs to do a arp lookup.
> 
> -- 
> Andre

Ah, my fault. I didn't read your patch carefully and assumed that ip
fastforward do flow caching as ip_flow does. However, I think ip flow
caching is a good thing and maybe implementing it in ip fastforward is
a good idea.

song


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree