Thread (4 messages) flat view 4 messages, 2 authors, 2012-05-10

Re: Fwd: Memory exhaust issue with only IPsec policies configured on continuous traffic

From: Nikhil Agarwal <hidden>
Date: 2012-05-10 09:43:19
Also in: lkml

Possibly related (same subject, not in this thread)

If i disable this cache of DST, dst are working fine. But now XFRM
state is allocated for every incoming packet and then freed. But while
freeing the xfrm state same garbage collection logic is there. Now
since packets are coming continuously garbage collector may not get
scheduled and large amount of memory is stuck to be freed causing the
system to go into non-recoverable state.

It seems that ther should be some change garbage collection scheduling
logic or  some mechnism to decide wether to cache some entry or not.

On Thu, May 10, 2012 at 11:02 AM, Eric Dumazet [off-list ref] wrote:
quoted hunk ↗ jump to hunk
On Thu, 2012-05-10 at 07:27 +0200, Eric Dumazet wrote:
quoted
Yep, we can use DST_NOCACHE
Please try following patch :
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 5773f5d..172c251 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -2896,6 +2896,7 @@ struct dst_entry *ipv4_blackhole_route(struct net *net, struct dst_entry *dst_or
       if (rt) {
               struct dst_entry *new = &rt->dst;

+               new->flags |= DST_NOCACHE;
               new->__use = 1;
               new->input = dst_discard;
               new->output = dst_discard;
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help