Re: Route caching ?



Actually there is:

struct route_in6 ip6_forward_rt;

that "caches" the last route used (thanks blue !!!) but i think this
technique is pointless in a multiflow traffic.

Is it reasonable to believe that route caches can improve networking
performance or we should leave it up to the routing table itself ?

On 8/22/07, Bruce M. Simpson <bms@xxxxxxxxxxx> wrote:
Not really, at least, not in the way one would think. rtalloc() is a
legacy function.

ip_output() will still call rtalloc() if you pass it a filled out
'struct route', a structure which is not a route, but an internal
request to look up a route.

This is a wrapper for rtalloc_ign(), which in turn is a wrapper for
rtalloc1(), the function which does the actual lookup.

rtalloc_ign() is pretty straightforward. Note however that this approach
only checks the RTF_UP flag and ifp, nothing more. This makes it
suitable for implementing floating statics, but nothing more dynamic
than that.

regards,
BMS



--
"UNIX is basically a simple operating system, but you have to be a
genius to understand the simplicity." Dennis Ritchie
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Route caching ?
    ... ip_outputwill still call rtalloc() if you pass it a filled out 'struct route', a structure which is not a route, but an internal request to look up a route. ... This is a wrapper for rtalloc_ign, which in turn is a wrapper for rtalloc1, the function which does the actual lookup. ...
    (freebsd-net)
  • Re: Route caching ?
    ... technique is pointless in a multiflow traffic. ... Is it reasonable to believe that route caches can improve networking ...
    (freebsd-net)
  • Re: Route caching ?
    ... that "caches" the last route used but i think this ... I believe that if one goes beyond a single radix trie, as is needed for multi-pathing with multicast and source policy routing, route caching is *required* to achieve good performance. ...
    (freebsd-net)
  • Re: Cached IP routes
    ... >> would be a correct fix, ... > just caches the route to the tunnel destination which normally stays ... > into are route changes. ... The result is that in_gif_outputcaches the default route ...
    (freebsd-net)
  • Re: CARP behaviour
    ... gredoes very funky things with the route it caches to the tunnel endpoint. ...
    (freebsd-net)