David Laight <David.Laight@xxxxxxxxxx> writes: > From: Eric W. Biederman >> Sent: 25 July 2018 18:38 > ... >> >> Further unless I misread something you are increasing the number of >> >> timers to 3 per namespace. If I create create a thousand network >> >> namespaces that feels like it will hurt system performance overall. >> > >> > It seems to me the timers are per neighbor entry not table. The per >> > table ones are for proxies. >> >> It seems I misread that bit when I was refreshing my memory on what >> everything is doing. If we can already have 1024 timers that makes >> timers not a concern. > > Surely it is enough to just have a timestamp in each entry. > Deletion of expired items need not be done until insert (which > has the table suitable locked) bumps into an expired item. Part of the state machine the timer is used for is sending retransmits before we get out first response, so the state machine is not just about expiry and may not be simple enough to do without a timer. I honestly don't remember the tradeoffs between the various kinds of timers. If we already can have up to 1000 timers without problems I suspect they are cheap enough optimizing for fewer times simply doesn't matter. Certainly we are not in regression territory if we don't. As for bumping into expired items on insert it would be a bad hash table if we were bumping into any other entries frequently on insert. Eric -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
