From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: nmreadelf <kong414@outlook.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, corbet@lwn.net, dsahern@kernel.org
Cc: horms@kernel.org, chia-yu.chang@nokia-bell-labs.com,
idosch@nvidia.com, ij@kernel.org, brauner@kernel.org,
jack@suse.cz, kuniyu@google.com, jlayton@kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, lance.yang@linux.dev,
leon.hwang@linux.dev
Subject: Re: [RFC PATCH net-next 0/3] netns: optionally inherit IPv4 TCP sysctls from old net
Date: Thu, 30 Apr 2026 17:44:53 +0200 [thread overview]
Message-ID: <3f8d63a3-e39e-48f9-a0d0-517be7c05498@6wind.com> (raw)
In-Reply-To: <TY7PR01MB172057C053E8D550485A29A08E0352@TY7PR01MB17205.jpnprd01.prod.outlook.com>
Le 30/04/2026 à 03:30, nmreadelf a écrit :
> a new network namespace starts with built-in TCP defaults.
> In container-heavy setups, operators often tune TCP sysctls in init_net and then
> need to re-apply the same values for each new netns.
>
> This series adds an opt-in mechanism to initialize per-netns IPv4 TCP sysctl
> settings from init_net at netns creation time.
>
> Behavior:
>
> Default is unchanged.
> When net.ipv4.netns_inherit_tcp_sysctls=1, new netns inherit
> TCP sysctl from old_net.
There is the same kind of sysctl for net.{ipv4,ipv6}.conf.{all,default}.*:
net.core.devconf_inherit_init_net.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/sysctl/net.rst#n401
I'm not sure if it's acceptable to use this existing entry to control the TCP
sysctl.
At least, putting the new one in the same place + using the same template for
the name + the same values would be nice. Something like
net.core.tcp_inherit_init_net.
Regards,
Nicolas
prev parent reply other threads:[~2026-04-30 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 1:30 [RFC PATCH net-next 0/3] netns: optionally inherit IPv4 TCP sysctls from old net nmreadelf
2026-04-30 1:32 ` nmreadelf
2026-04-30 1:33 ` [RFC PATCH net-next 1/3] ipv4: netns: group copyable TCP sysctls in netns_ipv4 nmreadelf
2026-04-30 1:33 ` [RFC PATCH net-next 2/3] net: ipv4: add netns_inherit_tcp_sysctls sysctl nmreadelf
2026-04-30 1:33 ` [RFC PATCH net-next 3/3] tcp: netns: optionally inherit IPv4 TCP sysctls from parent netns nmreadelf
2026-04-30 2:46 ` [RFC PATCH net-next 0/3] netns: optionally inherit IPv4 TCP sysctls from old net Eric Dumazet
2026-04-30 15:44 ` Nicolas Dichtel [this message]
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=3f8d63a3-e39e-48f9-a0d0-517be7c05498@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=brauner@kernel.org \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=ij@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=kong414@outlook.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=lance.yang@linux.dev \
--cc=leon.hwang@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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