ipv4: use separate genid for next hop exceptions
authorTimo Teräs <timo.teras@iki.fi>
Mon, 27 May 2013 20:46:33 +0000 (20:46 +0000)
committerDavid S. Miller <davem@davemloft.net>
Mon, 3 Jun 2013 07:07:43 +0000 (00:07 -0700)
commit5aad1de5ea2c260b4cd2f70b70e146d55dbbc528
treedbf8d674fb49a125cf547dd73726c33677d2081c
parentf016229e303c294afac721de4cd4427e634950ea
ipv4: use separate genid for next hop exceptions

commit 13d82bf5 (ipv4: Fix flushing of cached routing informations)
added the support to flush learned pmtu information.

However, using rt_genid is quite heavy as it is bumped on route
add/change and multicast events amongst other places. These can
happen quite often, especially if using dynamic routing protocols.

While this is ok with routes (as they are just recreated locally),
the pmtu information is learned from remote systems and the icmp
notification can come with long delays. It is worthy to have separate
genid to avoid excessive pmtu resets.

Cc: Steffen Klassert <steffen.klassert@secunet.com>
Signed-off-by: Timo Teräs <timo.teras@iki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/net/ip_fib.h
include/net/net_namespace.h
net/ipv4/route.c