Thread (10 messages) 10 messages, 5 authors, 2014-04-04

Re: IPv6 routing table max_size badly dimensioned compared to IPv4

From: David Miller <davem@davemloft.net>
Date: 2014-02-27 22:47:58

From: Eric Dumazet <redacted>
Date: Thu, 27 Feb 2014 13:02:00 -0800
On Thu, 2014-02-27 at 21:50 +0100, Hannes Frederic Sowa wrote:
quoted
We store those routes back into the routing table, so we must have a way to
count them and trigger gc at some point.
Right, and current implementation will not scale.

If we need to perform 10000 inserts per second, and gc timeout is 60
seconds, tree contains 600.000 entries, gc takes forever...
The only long term solution is to align ipv6 to be more like ipv4.

What's interesting is that if you look at the code, the original
author clearly intended to make callers be able to use route's
from the tree as-is without cloning.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help