From: Florian Westphal <fw@strlen.de>
To: menglong8.dong@gmail.com
Cc: kuba@kernel.org, christian.brauner@ubuntu.com,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
dong.menglong@zte.com.cn, daniel@iogearbox.net,
gnault@redhat.com, ast@kernel.org, nicolas.dichtel@6wind.com,
ap420073@gmail.com, edumazet@google.com, pabeni@redhat.com,
jakub@cloudflare.com, bjorn.topel@intel.com,
keescook@chromium.org, viro@zeniv.linux.org.uk, rdna@fb.com,
maheshb@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and sysctl_wmem_max
Date: Wed, 20 Jan 2021 11:46:21 +0100 [thread overview]
Message-ID: <20210120104621.GM19605@breakpoint.cc> (raw)
In-Reply-To: <20210118143932.56069-4-dong.menglong@zte.com.cn>
menglong8.dong@gmail.com <menglong8.dong@gmail.com> wrote:
> From: Menglong Dong <dong.menglong@zte.com.cn>
>
> 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
> per-namespace.
I think having those values be restricted by init netns is a desirable
property.
next prev parent reply other threads:[~2021-01-20 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:39 [PATCH net-next 0/3] Namespace-ify some sysctl in net/core menglong8.dong
2021-01-18 14:39 ` [PATCH net-next 1/3] net: core: init every ctl_table in netns_core_table menglong8.dong
2021-01-18 14:39 ` [PATCH net-next 2/3] net: core: Namespace-ify sysctl_wmem_default and sysctl_rmem_default menglong8.dong
2021-01-18 14:39 ` [PATCH net-next 3/3] net: core: Namespace-ify sysctl_rmem_max and sysctl_wmem_max menglong8.dong
2021-01-20 10:46 ` Florian Westphal [this message]
2021-01-20 13:28 ` Menglong Dong
2021-01-20 13:57 ` Nicolas Dichtel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210120104621.GM19605@breakpoint.cc \
--to=fw@strlen.de \
--cc=ap420073@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dong.menglong@zte.com.cn \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=jakub@cloudflare.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=rdna@fb.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).