[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2e1eaded-f9e0-0da8-4dd9-0d459470cc95@6wind.com>
Date: Wed, 20 Jan 2021 14:57:06 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: Menglong Dong <menglong8.dong@...il.com>,
Florian Westphal <fw@...len.de>
Cc: Jakub Kicinski <kuba@...nel.org>, christian.brauner@...ntu.com,
David Miller <davem@...emloft.net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Menglong Dong <dong.menglong@....com.cn>, daniel@...earbox.net,
gnault@...hat.com, ast@...nel.org, ap420073@...il.com,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, jakub@...udflare.com,
bjorn.topel@...el.com, Kees Cook <keescook@...omium.org>,
viro@...iv.linux.org.uk, rdna@...com,
Mahesh Bandewar <maheshb@...gle.com>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and
sysctl_wmem_max
Le 20/01/2021 à 14:28, Menglong Dong a écrit :
[snip]
>>> For that reason, make sysctl_wmem_max and sysctl_rmem_max
>>> per-namespace.
>>
>> I think having those values be restricted by init netns is a desirable
>> property.
>
> I just thought that having these values per-namespace can be more flexible,
> and users can have more choices. Is there any bad influence that I didn't
> realize?
You can have a look here:
https://lore.kernel.org/netdev/1501495652.1876.17.camel@edumazet-glaptop3.roam.corp.google.com/
https://patchwork.ozlabs.org/project/netdev/patch/20170726170333.24580-1-mcroce@redhat.com/
Regards,
Nicolas
Powered by blists - more mailing lists