[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131028113039.GE31491@secunet.com>
Date: Mon, 28 Oct 2013 12:30:39 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Wolfgang Walter <linux@...m.de>,
David Miller <davem@...emloft.net>, hannes@...essinduktion.org,
netdev@...r.kernel.org, klassert@...hematik.tu-chemnitz.de
Subject: Re: Big performance loss from 3.4.63 to 3.10.13 when routing ipv4
On Sun, Oct 27, 2013 at 11:17:31PM -0700, Eric Dumazet wrote:
> On Fri, 2013-10-25 at 11:20 +0200, Steffen Klassert wrote:
> > On Fri, Oct 25, 2013 at 01:50:28AM -0700, Eric Dumazet wrote:
> > >
> > > 32768 as the default seems fine to me
> > >
> > > 448 bytes per dst -> thats less than 30 Mbytes of memory if we hit 65536
> > > dst.
> > >
> >
> > Ok, I'll add the patch below to to the ipsec tree if everyone is fine
> > with that threshold.
> >
> > Subject: [PATCH RFC] 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.
> >
> > Signed-off-by: Steffen Klassert <steffen.klassert@...unet.com>
> > ---
>
> Sure please add :
>
> Reported-by: Wolfgang Walter <linux@...m.de>
Done.
Now applied to the ipsec tree, thanks everyone!
--
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