From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] net: do not create fallback tunnels for non-default namespaces
Date: Fri, 09 Mar 2018 11:23:50 -0500 (EST) [thread overview]
Message-ID: <20180309.112350.1061969650325938370.davem@davemloft.net> (raw)
In-Reply-To: <20180308205141.77868-1-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Thu, 8 Mar 2018 12:51:41 -0800
> fallback tunnels (like tunl0, gre0, gretap0, erspan0, sit0,
> ip6tnl0, ip6gre0) are automatically created when the corresponding
> module is loaded.
>
> These tunnels are also automatically created when a new network
> namespace is created, at a great cost.
>
> In many cases, netns are used for isolation purposes, and these
> extra network devices are a waste of resources. We are using
> thousands of netns per host, and hit the netns creation/delete
> bottleneck a lot. (Many thanks to Kirill for recent work on this)
>
> Add a new sysctl so that we can opt-out from this automatic creation.
>
> Note that these tunnels are still created for the initial namespace,
> to be the least intrusive for typical setups.
>
> Tested:
...
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks Eric.
prev parent reply other threads:[~2018-03-09 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 20:51 [PATCH net-next] net: do not create fallback tunnels for non-default namespaces Eric Dumazet
2018-03-09 11:06 ` Jiri Benc
2018-03-09 12:53 ` Eric Dumazet
2018-03-09 13:08 ` Jiri Benc
2018-03-09 13:18 ` Eric Dumazet
2018-03-09 16:23 ` David Miller [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=20180309.112350.1061969650325938370.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).