Hi,
I noticed a discussion on netdev
with someone getting dst cache overflow errors; I've been experiencing
similar things on a router - it has died 3 or 4 times (over a period
of a few months) with such an error with very little traffic passing
through it and a stream of the 'dst cache overflow' errors on the screen.
Currently it is running a 2.6.10 and from the discussions it looks
worth while bringing that upto a 2.6.12, also someone suggested to me
a patch by Denis Lunev that is currently in one of the 2.6.13-pre's
('Fix too aggressive backoff in dst garbage collection' git commit number
f0098f7863f814a5adc0b9cb271605d063cad7fa )
I'll give those a go, but I wondered if there was a general set of
diag/monitoring that would be useful so that if it does it again I can
present some useful debug? At the moment I have a rtstat 60 running into
a log file.
The machine is a single processor machine with 3 network cards (2xgig
e1000, 1x100mbps e100 I think) routing between two internal networks
(on the e1000s) and to a seperate firewall.
Dave
P.S. Is there a good description of how these caches work? I was looking
at dst.c and route.c and they both seem to have garbage collection
mechanisms and the 'dst cache overflow' comes from the ipv4/route.c -
at this point I'm rather confused between the relationship of the code
in dst.c and that in route.c and all the various garbage collection that
goes on.
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
