I lowered the timeout to make gc more agressive. Though, it can still
be adjusted via a /proc entry. Default was 300. Increasing the other
parameters that you specified (which I have done) only delays the
inevitable "dst cache overflow". The problem is that gc (rather
rt_free) is not decrementing .entries. So it _thinks_ the table
has overflown.
chad
> -----Original Message-----
> From: owner-netdev@xxxxxxxxxxx@YRINC On Behalf Of jamal
> <hadi@xxxxxxxxxx>
> Sent: Sunday, April 14, 2002 3:44 PM
> To: Milam, Chad
> Cc: netdev@xxxxxxxxxxx
> Subject: Re: dst cache overflow 2.2.x; x>=16
>
>
>
> On Sun, 14 Apr 2002, jamal wrote:
>
> >
> > Hi,
> >
> > Why couldnt you just modify the parameters in /proc?
> >
> > -Increase the overflow threshold (you actually hardcode this)
> > /proc/sys/net/ipv4/route/gc_thresh
> > -decrease the gc timer
> > /proc/sys/net/ipv4/route/gc_timeout
>
> Sorry, you hardcoded /proc/sys/net/ipv4/route/gc_timeout
> to 120 secs.
>
> cheers,
> jamal
>
|