On Tue, Aug 1, 2017, at 09:18, Eric Dumazet wrote:
> On Tue, 2017-08-01 at 02:17 -0400, Hannes Frederic Sowa wrote:
>
> > We do account rmem as well as wmem allocated memory to the apropriate
> > mem_cgs. In theory this should be okay.
>
> Last time I checked, rmem was not memcg ready yet.
>
> C
On Tue, 2017-08-01 at 02:17 -0400, Hannes Frederic Sowa wrote:
> We do account rmem as well as wmem allocated memory to the apropriate
> mem_cgs. In theory this should be okay.
Last time I checked, rmem was not memcg ready yet.
Can you describe the details ?
Thanks.
Eric Dumazet writes:
> On Wed, 2017-07-26 at 19:03 +0200, Matteo Croce wrote:
>> The following sysctl are global and can't be read or set from a netns:
>>
>> net.core.rmem_default
>> net.core.rmem_max
>> net.core.wmem_default
>> net.core.wmem_max
>>
>> Make the following sysctl parameters avail
On Wed, 2017-07-26 at 19:03 +0200, Matteo Croce wrote:
> The following sysctl are global and can't be read or set from a netns:
>
> net.core.rmem_default
> net.core.rmem_max
> net.core.wmem_default
> net.core.wmem_max
>
> Make the following sysctl parameters available from within a network
> name
Matteo Croce writes:
> The following sysctl are global and can't be read or set from a netns:
>
> net.core.rmem_default
> net.core.rmem_max
> net.core.wmem_default
> net.core.wmem_max
[...]
I think a sensible addition to those sysctls would be
tcp_moderate_rcvbuf to disable autotuning.
Thanks!
The following sysctl are global and can't be read or set from a netns:
net.core.rmem_default
net.core.rmem_max
net.core.wmem_default
net.core.wmem_max
Make the following sysctl parameters available from within a network
namespace, allowing to set unique values per network namespace.
My concern i
