tcp hostcache and ip fastforward for review

[popsong old]

--- Andre Oppermann <oppermann at 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