[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200626.130029.89317239393030387.davem@davemloft.net>
Date: Fri, 26 Jun 2020 13:00:29 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: horatiu.vultur@...rochip.com
Cc: nikolay@...ulusnetworks.com, roopa@...ulusnetworks.com,
kuba@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink
interface with IFLA_BRIDGE_MRP_CLEAR
From: Horatiu Vultur <horatiu.vultur@...rochip.com>
Date: Fri, 26 Jun 2020 09:33:47 +0200
> This patch series extends MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR.
> To allow the userspace to clear all MRP instances when is started. The
> second patch in the series fix different sparse warnings.
>
> v3:
> - add the second patch to fix sparse warnings
These changes are completely unrelated.
The sparse stuff should probably be submitted to 'net'.
And I have to ask why you really need a clear operation. Routing
daemons come up and see what routes are installed, and update their
internal SW tables to match. This not only allows efficient restart
after a crash, but it also allows multiple daemons to work
cooperatively as an agent for the same forwarding/routing table.
Your usage model limits one daemon to manage the table and that
limitation is completely unnecessary.
Furthermore, even in a one-daemon scenerio, it's wasteful to throw
away all the work the previous daemon did to load the MRP entries into
the bridge.
Thanks.
Powered by blists - more mailing lists