From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] tcp: Namespace-ify sysctl_tcp_default_congestion_control Date: Mon, 13 Nov 2017 10:27:00 +0900 (KST) Message-ID: <20171113.102700.2072956247690538502.davem@davemloft.net> References: <20171110012637.2454-1-sthemmin@microsoft.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: edumazet@google.com, netdev@vger.kernel.org, sthemmin@microsoft.com To: stephen@networkplumber.org Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:45884 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751329AbdKMB1D (ORCPT ); Sun, 12 Nov 2017 20:27:03 -0500 In-Reply-To: <20171110012637.2454-1-sthemmin@microsoft.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Stephen Hemminger Date: Fri, 10 Nov 2017 10:26:37 +0900 > Make default TCP default congestion control to a per namespace > value. The congestion control setting of new namespaces is inherited > from the root namespace. Modules are only autoloaded in the root namespace. > > Signed-off-by: Stephen Hemminger I have to think some more about this and the semantics you've choosen. Is it really buying us anything to restrict the module load to the initial namespace? Unless it's really required this makes things like running tests in sub-namespaces unnecessarily cumbersome.