Daniel Lezcano wrote:
So you prefer to have multiple timers flushing a portion of a shared
routing cache ?
It is not impossible I already tryed that for ipv6. it will just touch
much more files.
If we want, at all costs, to have the routing cache flushed per
namespace, I am much more favorable to have a timer per namespace than
using the algorithm you sent previously.
as do I. But the IPv4 and IPv6 situation is much different. IPv6 cache
is separated while IPv4 one is common.
So, the situation is not uniform, at least :(
By the way, we can move routing cache into the FIB tree like one for IPv4 :)
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers
