[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1324397163-302-1-git-send-email-madalin.bucur@freescale.com>
Date: Tue, 20 Dec 2011 18:06:03 +0200
From: Madalin Bucur <madalin.bucur@...escale.com>
To: <steffen.klassert@...unet.com>
CC: <davem@...emloft.net>, <eric.dumazet@...il.com>,
<timo.teras@....fi>, <netdev@...r.kernel.org>
Subject:
Hi Steffen,
I did not have the time to test and send a v2 for my patch to remove the leftover local_bh_disable()/local_bh_enable() Ben has spotted.
I've also tried to use your approach but in my tests, under high load, the defered work was defered forever...
I'll try to test again with your patch and confirm it does not suffer from this issue or send a patch with those local_bh removed.
Madalin
-----Original Message-----
From: Steffen Klassert [mailto:steffen.klassert@...unet.com]
Sent: Tuesday, December 20, 2011 10:24 AM
To: David Miller
Cc: Bucur Madalin-Cristian-B32716; eric.dumazet@...il.com; netdev@...r.kernel.org; timo.teras@....fi
Subject: Re: [PATCH] net/flow: remove sleeping and deferral mechanism from flow_cache_flush
On Tue, Sep 27, 2011 at 03:31:32PM -0400, David Miller wrote:
> From: David Miller <davem@...emloft.net>
> Date: Tue, 27 Sep 2011 15:28:36 -0400 (EDT)
>
> > afinfo->garbage_collect is the only other place
> > afinfo->__xfrm_garbage_collect
> > is referenced, and that is completely unused and should thus be
> > deleted (I'll take care of that in net-next).
>
> Nevermind I see how these are referenced directly via xfrm4_policy.c
> and xfrm6_policy.c, sigh...
Is there any progress in fixing this issue? I've seen this occasionally on some of our production systems, so I fixed it for us in the meantime with the patch below. I could submit this for inclusion if noone else wants to fix it in a different manner.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists