Subject: Re: [RFC PATCH] dont create cached routes from ARP requests

From: Ulrich Weber <[email-masked]>
Date: Fri, 24 Sep 2010 17:00:12 +0200

Hi Eric,

please find the output in the attached text file.

Neighbor garbage collection wont't work because all
neighbor records are bound to cached routes.

Forced route garbaged collections returns without freeing
any routes, probably because the route threshold is quite high
with 65536 compared to the small neighbor threshold of 1024,
resulting in a fixed amount of 1024 cached routes...

Instead of running the garbage collection we could flush the route
cache completely if the neighbor cache overflows.
But why do we have to cache that routes in first place ?
See the previous patch which skips caching for that kind of routes.

Cheers
 Ulrich