Messages in this thread |  | | Date | Fri, 13 Oct 2000 01:01:35 +0200 | From | Andi Kleen <> | Subject | Re: dst cache overflow |
| |
On Thu, Oct 12, 2000 at 12:39:09PM -0400, Ed Taranto wrote: > Anyone out there have any further information or insight into this?
You can check the routes in the rtcache by using route --cache. Maybe you can see a pattern.
> > One thing that concerns me is that rt_garbage_collect will only make one > pass through the main loop while in_interrupt() ... thus perhaps that is > why it doesn't make it's goal of getting the cache entries below > ip_rt_max_size. if i am under heavy load, perhaps i am spending too much > time in_interrupt() which is why I can't trim down the cache sufficiently??
For a router/packet filter firewall rt_garbage_collect will only be called from interrupt context. Normally a single sweep should be more than enough though.
> Or does this perhaps sound like a memory leak or something?
A common cause are port scans which cause generation of lots of routes very quickly.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |