Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp67660imm; Tue, 17 Jul 2018 21:00:32 -0700 (PDT) X-Google-Smtp-Source: AAOMgpf2AAupzTTeTHLcLitwM2mZlGxwjpL5Pyr2NobZw7keYHaeTmOPnWxcnfVZ+Qe5/BWDpwTE X-Received: by 2002:a17:902:f83:: with SMTP id 3-v6mr4236366plz.282.1531886432177; Tue, 17 Jul 2018 21:00:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531886432; cv=none; d=google.com; s=arc-20160816; b=W1gmQOkpqIxain39bwFJCpWs6yDp6Ysqs8yI7jrwAbLqJFuTkLYgn8AcHoU7hUI/25 CMKJ7LGG04JN7ZXMARwaPrmVbILnXvAvWQdXWBhCuONhQMJsW3crOLDimZmzyFoyPrIU GEd1gmk9vVGCeqK4NXvSr5ttzO3Odnha0uwjQmatNj/uHxYpJcXGjSXWEe1JOYPsaavG FqT69s/9opRXjcYA0lgNEEW7gnHYLn3z9ODDKG5xnoMQB1WhklpGMfQ7Zewe2kL48V5l kaMqhIs/lBOPY8WTHY7EG4Xf8hgmLASipwNhaMbbBorAPsZn3cdejw6A/jbmDpt67u96 yDqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=xyM3BT20qLyQMACYyQp63QRRk8zvn+QX2XG1N2HEnZU=; b=OTfjBGylocUWftiwPFEgQZPwXMzija1XSLegGaKsTL7MiBGeQrXGXOsSflmqReOYde sWybBlM4rzhED10+Z+Wm0aX4ZjUMchIn1Sw9yxFxshG1Zks06yZozCnjtHf4p+cPYyq3 /e4yXK5vcgHX3EgkCxDqZIcYI64cAIuRSnMDjIPB3NSFAQ8anXWTcMuqHaLqOUBSMAOS H2iRN0KSpMYhDeOsrv/03tc825r7NCJ10H1MsSleSG0z8FTi0JWdbAOGVEEfRsTfSkZg YP1i849MRkCgsV10Nm5rHRPKHr+pApgZVuwP7jy2OZCemegzmPrScAhHWYX+2oBFAHLr 2pMQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v9-v6si2516179pfg.123.2018.07.17.21.00.16; Tue, 17 Jul 2018 21:00:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726159AbeGREfb (ORCPT + 99 others); Wed, 18 Jul 2018 00:35:31 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:56768 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725730AbeGREfa (ORCPT ); Wed, 18 Jul 2018 00:35:30 -0400 Received: from localhost (unknown [172.58.43.84]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id DC744100858FB; Tue, 17 Jul 2018 20:59:40 -0700 (PDT) Date: Wed, 18 Jul 2018 12:59:38 +0900 (KST) Message-Id: <20180718.125938.2271502580775162784.davem@davemloft.net> To: dsahern@gmail.com Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org, nikita.leshchenko@oracle.com, roopa@cumulusnetworks.com, stephen@networkplumber.org, idosch@mellanox.com, jiri@mellanox.com, saeedm@mellanox.com, alex.aring@gmail.com, linux-wpan@vger.kernel.org, netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC/RFT net-next 00/17] net: Convert neighbor tables to per-namespace From: David Miller In-Reply-To: <1a27e301-3275-b349-a2f8-afdfdc02f04f@gmail.com> References: <1a3f59a9-0ba5-c83f-16a6-f9550a84f693@gmail.com> <1a27e301-3275-b349-a2f8-afdfdc02f04f@gmail.com> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 17 Jul 2018 20:59:41 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: David Ahern Date: Tue, 17 Jul 2018 13:02:18 -0600 > I understand the concern about global resource and limits: as it stands > you have to increase the limits in init_net to the max expected and hope > for the best. With per namespace limits you can lower the limits of each > namespace better control the total impact on the total memory used. > Perhaps the defaults for namespaces after init_net could have really low > defaults (e.g., 16 / 32 / 64 for gc_thresh 1/2/3) requiring admin > intervention. How does this work when a namespace creates another namespace? Changing the defaults for non-init_net namespaces could work, but that could be a surprise to some people.