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)
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

index ccde54248c8ca77d3efc173ce457aa5f0153337a..4764ee48447caead484577f0ac204160f899763c 100644 (file)
@@ -236,7 +236,7 @@ static struct dst_ops xfrm4_dst_ops = {
        .destroy =              xfrm4_dst_destroy,
        .ifdown =               xfrm4_dst_ifdown,
        .local_out =            __ip_local_out,
-       .gc_thresh =            1024,
+       .gc_thresh =            32768,
 };
 
 static struct xfrm_policy_afinfo xfrm4_policy_afinfo = {
index 08ed2772b7aa58225bd6be95518ea95c1191dcd9..dd503a3535ff18c94b3fcb3c14d364e264912b7a 100644 (file)
@@ -285,7 +285,7 @@ static struct dst_ops xfrm6_dst_ops = {
        .destroy =              xfrm6_dst_destroy,
        .ifdown =               xfrm6_dst_ifdown,
        .local_out =            __ip6_local_out,
-       .gc_thresh =            1024,
+       .gc_thresh =            32768,
 };
 
 static struct xfrm_policy_afinfo xfrm6_policy_afinfo = {