[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191002.115219.1233859945590634038.davem@davemloft.net>
Date: Wed, 02 Oct 2019 11:52:19 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, idosch@...lanox.com, pabeni@...hat.com,
edumazet@...gle.com, petrm@...lanox.com, sd@...asysnail.net,
f.fainelli@...il.com, stephen@...workplumber.org,
mlxsw@...lanox.com
Subject: Re: [patch net-next 0/3] net: introduce per-netns netdevice
notifiers and use them in mlxsw
From: Jiri Pirko <jiri@...nulli.us>
Date: Mon, 30 Sep 2019 10:15:08 +0200
> From: Jiri Pirko <jiri@...lanox.com>
>
> Some drivers, like mlxsw, are not interested in notifications coming in
> for netdevices from other network namespaces. So introduce per-netns
> notifiers and allow to reduce overhead by listening only for
> notifications from the same netns.
>
> This is also a preparation for upcoming patchset "devlink: allow devlink
> instances to change network namespace". This resolves deadlock during
> reload mlxsw into initial netns made possible by
> 328fbe747ad4 ("net: Close race between {un, }register_netdevice_notifier() and setup_net()/cleanup_net()").
Series applied.
Powered by blists - more mailing lists