From: Steffen Klassert <steffen.klassert@secunet•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Damian Pietras <damianp@daper•net>, netdev@vger•kernel.org
Subject: Re: "xfrm: Fix the gc threshold value for ipv4" broke my IPSec connections
Date: Wed, 16 Oct 2013 13:35:00 +0200 [thread overview]
Message-ID: <20131016113500.GA7660@secunet.com> (raw)
In-Reply-To: <1381877486.2045.78.camel@edumazet-glaptop.roam.corp.google.com>
On Tue, Oct 15, 2013 at 03:51:26PM -0700, Eric Dumazet wrote:
> On Wed, 2013-10-16 at 00:15 +0200, Damian Pietras wrote:
> > On 15.10.2013 23:02, Eric Dumazet wrote:
> > >> 703fb94ec58e0e8769380c2877a8a34aeb5b6c97
> > >> xfrm: Fix the gc threshold value for ipv4
> > >>
> > >> Reverting it on 3.10.15 fixes my issue. This seems to be there from 3.7
> > >> and I don't really believe such simple case stayed broken for so long.
> > >> Em I missing something or there is really a bug?
> > >>
> > >> If smeone is interested in details of this configuration and commands
> > >> I'm running, just let me know. This was reproduced with few VMs under XEN.
> > >>
> > >
> > > It looks like you need to tune /proc/sys/net/ipv4/xfrm4_gc_thresh to a
> > > sensible value given your workload.
> > >
> > > try :
> > >
> > > echo 65536 >/proc/sys/net/ipv4/xfrm4_gc_thresh
> > >
> > > Presumably the 1024 default is really too small...
> >
> > Now it's working in my test setup, I'm changing it on the production
> > boxes, thanks!
> >
> >
>
> Steffen, what do you think ?
>
> 1024 seems really small, given we had much higher values.
Sure, we can increase the default value, maybe along with the ipv6 side.
Any recomendation on a good default for both?
>
> (256 K on a 1GB host)
>
> This sysctl also needs an entry in
> Documentation/networking/ip-sysctl.txt
>
Yes, it's undocumented. I'll take care of it.
prev parent reply other threads:[~2013-10-16 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 20:40 "xfrm: Fix the gc threshold value for ipv4" broke my IPSec connections Damian Pietras
2013-10-15 21:02 ` Eric Dumazet
2013-10-15 22:15 ` Damian Pietras
2013-10-15 22:51 ` Eric Dumazet
2013-10-16 11:35 ` Steffen Klassert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131016113500.GA7660@secunet.com \
--to=steffen.klassert@secunet$(echo .)com \
--cc=damianp@daper$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox