From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:53376 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751147AbeCIQXw (ORCPT ); Fri, 9 Mar 2018 11:23:52 -0500 Date: Fri, 09 Mar 2018 11:23:50 -0500 (EST) Message-Id: <20180309.112350.1061969650325938370.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 From: David Miller In-Reply-To: <20180308205141.77868-1-edumazet@google.com> References: <20180308205141.77868-1-edumazet@google.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: From: Eric Dumazet 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 Applied, thanks Eric.