| To: | "Milam, Chad" <Chad_Milam@xxxxxxxxxx> |
|---|---|
| Subject: | RE: dst cache overflow 2.2.x; x>=16 |
| From: | Robert Olsson <Robert.Olsson@xxxxxxxxxxx> |
| Date: | Mon, 15 Apr 2002 23:47:07 +0200 |
| Cc: | <netdev@xxxxxxxxxxx>, "Julian Anastasov <ja@xxxxxx>" <IMCEANOTES-+22Julian+20Anastasov+20+3Cja+40ssi+2Ebg+3E+22@xxxxxxxxxxxxxxx> |
| In-reply-to: | <D4CA6B275AA33241AC771F0C0B43A921011BE86B@nyc285ex01.nyc.corp.yr.com> |
| References: | <D4CA6B275AA33241AC771F0C0B43A921011BE86B@nyc285ex01.nyc.corp.yr.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Milam, Chad writes: > > The box is a router, no ip masq, no ip chains, no ip fw, just a router. Weird. Julian has a useful program testlvs for testing route cache. I just tested this w. linux-2.2.17 many srcnum (80000) but cannot force cache overflow. Ok it was not for hours. And 2.2.X has recent cache code I was wrong here. I have used it for just for routers for pretty demanding jobs. I would look for grows in /proc/slabinfo too...
With the patch you can monitor ipv4_dst_ops.entries wich rtstat and
testlvs is good exerciser.
Cheers.
--ro
BTW. I think rtstat can hold have some stats about the GC process too.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: dst cache overflow 2.2.x; x>=16, Milam, Chad |
|---|---|
| Next by Date: | a question on loopback, wangxiangyu |
| Previous by Thread: | RE: dst cache overflow 2.2.x; x>=16, Milam, Chad |
| Next by Thread: | Re: addrconf.c - possible bug, Petr Baudis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |