| To: | "Milam, Chad" <Chad_Milam@xxxxxxxxxx> |
|---|---|
| Subject: | RE: dst cache overflow 2.2.x; x>=16 |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Sun, 14 Apr 2002 16:53:30 -0400 (EDT) |
| Cc: | <netdev@xxxxxxxxxxx> |
| In-reply-to: | <D4CA6B275AA33241AC771F0C0B43A921011BE867@nyc285ex01.nyc.corp.yr.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
If i summarize your problem is that you are building up dst caches faster than they can be garbage collected. Solution 1. Make the max size large enough to catchup with rate 2. Make sure that every time you go into garbage collection you are successful. - reducing the min interval to 1 might be a little aggressive. But you can tune this later - You wanna make sure you get a large positive "goal" every time play with ip_rt_gc_elasticity (/proc/sys/net/ipv4/route/gc_elasticity) also the rt_hash_log All the above are configurable via /proc have to run cheers, jamal |
| <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: | RE: dst cache overflow 2.2.x; x>=16, Robert Olsson |
| Previous by Thread: | RE: dst cache overflow 2.2.x; x>=16, Milam, Chad |
| Next by Thread: | RE: dst cache overflow 2.2.x; x>=16, Robert Olsson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |