From: Ido Schimmel <idosch@nvidia.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>, Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v6 net-next 00/15] neighbour: Namespacify arp_tbl and nd_tbl.
Date: Thu, 3 Sep 2026 15:46:54 +0300 [thread overview]
Message-ID: <20260903124654.GA128168@shredder> (raw)
In-Reply-To: <20260902203722.926528-1-kuniyu@google.com>
On Wed, Sep 02, 2026 at 08:36:41PM +0000, Kuniyuki Iwashima wrote:
> The neighbour subsystem is almost ready to drop RTNL.
>
> However, the control paths are serialised by the global
> per-table lock.
>
> This series converts arp_tbl and nd_tbl to per-netns table.
>
> With the series, /proc/sys/net/ipv{4,6}/neigh/default/ can
> be configured per netns, which was only configurable in
> init_net.
>
> To avoid potential regression, all the settings are inherited
> from init_net by default, and this behaviour is controlled by
> a new sysctl knob, net.core.neigh_inherit_init_net:
>
> # sysctl net.core.neigh_inherit_init_net
> net.core.neigh_inherit_init_net = 1
> # sysctl net.ipv4.neigh.default.gc_thresh1
> net.ipv4.neigh.default.gc_thresh1 = 128
> # sysctl net.ipv4.neigh.default.gc_thresh1=129
> net.ipv4.neigh.default.gc_thresh1 = 129
> # unshare -n sysctl net.ipv4.neigh.default.gc_thresh1
> net.ipv4.neigh.default.gc_thresh1 = 129
>
> If it is turned off, all settings are reset in the new netns:
>
> # sysctl net.core.neigh_inherit_init_net=0
> net.core.neigh_inherit_init_net = 0
> # unshare -n sysctl net.ipv4.neigh.default.gc_thresh1
> net.ipv4.neigh.default.gc_thresh1 = 128
>
> Series overview:
>
> Patch 1 deflakes test_neigh.sh.
>
> Patch 2 ~ 3 are misc cleanup.
>
> Patch 4 ~ 7 store arp_tbl/nd_tbl to net->neigh_tables[] and
> remove the global neigh_tables[].
>
> Patch 8 ~ 9 replace the direct access to arp_tbl/nd_tbl to
> net->neigh_tables[] using new helpers.
>
> Patch 10 ~ 12 finally replace the global table with per-netns
> table.
>
> Patch 13 ~ 14 clean up unnecessary net_eq().
>
> Patch 15 updates test_neigh.sh.
>
> Note that some buggy drivers access nd_tbl without checking
> disable_ipv6_mod, so nd_tbl's extern definition is still left.
>
> After this series, I will follow up on two suggestions by Ido:
> https://lore.kernel.org/netdev/20260902143023.GA3966681@shredder/
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Thanks!
next prev parent reply other threads:[~2026-09-03 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 20:36 [PATCH v6 net-next 00/15] neighbour: Namespacify arp_tbl and nd_tbl Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 01/15] selftest: net: Deflake Periodic GC test in test_neigh.sh Kuniyuki Iwashima
2026-09-04 3:09 ` netdev-bot+sashiko
2026-09-02 20:36 ` [PATCH v6 net-next 02/15] neighbour: Remove __neigh_for_each_release() Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 03/15] neighbour: Remove lock dance for neigh_update_{gc,managed}_list() Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 04/15] neighbour: Remove unnecessary EXPORT_SYMBOL() Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 05/15] neighbour: Remove __rcu from neigh_tables[] Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 06/15] neighbour: Store arp_tbl and nd_tbl in net->neigh_tables[] Kuniyuki Iwashima
2026-09-04 3:09 ` netdev-bot+sashiko
2026-09-02 20:36 ` [PATCH v6 net-next 07/15] neighbour: Remove neigh_tables[] Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 08/15] ipv4: Replace &arp_tbl with arp_table(net) Kuniyuki Iwashima
2026-09-04 3:09 ` netdev-bot+sashiko
2026-09-04 16:16 ` Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 09/15] ipv6: Replace &nd_tbl with nd_table(net) Kuniyuki Iwashima
2026-09-04 3:09 ` netdev-bot+sashiko
2026-09-04 16:36 ` Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 10/15] neighbour: Clean up neigh_table_init() and neigh_table_clear() Kuniyuki Iwashima
2026-09-04 3:10 ` netdev-bot+sashiko
2026-09-04 16:28 ` Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 11/15] neighbour: Convert neigh_table.entries to refcount_t Kuniyuki Iwashima
2026-09-04 3:10 ` netdev-bot+sashiko
2026-09-04 16:39 ` Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 12/15] neighbour: Namespacify neigh_tables Kuniyuki Iwashima
2026-09-04 3:10 ` netdev-bot+sashiko
2026-09-04 16:44 ` Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 13/15] neighbour: Don't store net in struct pneigh_entry Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 14/15] neighbour: Remove unnecessary net_eq() Kuniyuki Iwashima
2026-09-02 20:36 ` [PATCH v6 net-next 15/15] selftest: net: Specify netns for ip ntable in test_neigh.sh Kuniyuki Iwashima
2026-09-04 3:10 ` netdev-bot+sashiko
2026-09-04 16:46 ` Kuniyuki Iwashima
2026-09-03 12:46 ` Ido Schimmel [this message]
2026-09-04 22:20 ` [PATCH v6 net-next 00/15] neighbour: Namespacify arp_tbl and nd_tbl patchwork-bot+netdevbpf
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=20260903124654.GA128168@shredder \
--to=idosch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--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