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

Re: [PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and sysctl_wmem_max

Hello~ On Wed, Jan 20, 2021 at 6:46 PM Florian Westphal wrote: > > > > > 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

Re: [PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and sysctl_wmem_max

menglong8.d...@gmail.com wrote: > From: Menglong Dong > > For now, sysctl_wmem_max and sysctl_rmem_max are globally unified. > It's not convenient in some case. For example, when we use docker > and try to control the default udp socket receive buffer for each > container. > > For that reason,

[PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and sysctl_wmem_max

From: Menglong Dong For now, sysctl_wmem_max and sysctl_rmem_max are globally unified. It's not convenient in some case. For example, when we use docker and try to control the default udp socket receive buffer for each container. For that reason, make sysctl_wmem_max and sysctl_rmem_max