Hello, On 30 Sep 2002, William L. Thomson Jr. wrote: > I will go in order and below are the values I last tested, and the > default values. > # Default Values > #echo 256 > /proc/sys/net/ipv4/route/gc_elasticity # 8 gc_elasticity can be 1..16, gc_elasticity*gc_thresh is the desired number of entries we can live with, after that point we start to worry about filling the cache. > #echo 1 > /proc/sys/net/ipv4/route/gc_interval # 60 > #echo 0 > /proc/sys/net/ipv4/route/gc_timeout # 300 On each interval (gc_interval) up to gc_interval/gc_timeout entries are checked for expiration. With the default parameters, 1/5 of the table on each 60sec, each cache entry lives up to 300sec by default. > #echo 0 > /proc/sys/net/ipv4/route/gc_min_interval # 5 gc_min_interval 0 means no restrictions for running GC, may be it is good on load. > #echo 128 > /proc/sys/net/ipv4/route/gc_thresh # 256 > #echo 1 > /proc/sys/net/ipv4/route/max_delay # 10 > #echo 1 > /proc/sys/net/ipv4/route/min_delay # 2 > #echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter # 1 > #echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter # 1 > The gc_timeout seems to be a timeout between gc's? this is gc_interval Regards -- Julian Anastasov <ja@ssi.bg> _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
