xfrm: Increase the garbage collector threshold
authorSteffen Klassert <steffen.klassert@secunet.com>
Fri, 25 Oct 2013 08:21:32 +0000 (10:21 +0200)
committerSteffen Klassert <steffen.klassert@secunet.com>
Mon, 28 Oct 2013 06:37:52 +0000 (07:37 +0100)
commiteeb1b73378b560e00ff1da2ef09fed9254f4e128
tree6974add0fb4340478f299a41230c1cb422e81324
parent12e3594698f6c3ab6ebacc79f2fb2ad2bb5952b5
xfrm: Increase the garbage collector threshold

With the removal of the routing cache, we lost the
option to tweak the garbage collector threshold
along with the maximum routing cache size. So git
commit 703fb94ec ("xfrm: Fix the gc threshold value
for ipv4") moved back to a static threshold.

It turned out that the current threshold before we
start garbage collecting is much to small for some
workloads, so increase it from 1024 to 32768. This
means that we start the garbage collector if we have
more than 32768 dst entries in the system and refuse
new allocations if we are above 65536.

Reported-by: Wolfgang Walter <linux@stwm.de>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
net/ipv4/xfrm4_policy.c
net/ipv6/xfrm6_policy.c