On Mon, Jun 02, 2003 at 06:36:37PM +0200, Robert Olsson wrote: > We are given more work than we have resources for (max_size) what else than > refuse can we do? But yes we have invested pretty much work already. Well, this is the problem. We do not and cannot know which entries we really want to remember (legitimate traffic). Adding code to actually refuse new dst entries is just going to make the DoS effective, which is NOT what we want. > Also remember we are looking into runs were 100% of incoming traffic has one > new dst for every packet. So how is the situation in "real life"? > In case of multiple devices at least NAPI gives all devs it's share. Right, so, when we are traffic saturated, we want to make sure the whole route cache and route path is as fast as possible. Recycling dst entries by simpy rewriting and rehashing them rather than allocating new and eventually freeing them all in the garbage collection cycle should reduce allocator overhead. If this is only done when the table is full, I don't see any downside...if this is in fact doable, that is. :) Simon- - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
