[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXkK5jp7FHwJEeuw@shredder>
Date: Wed, 27 Oct 2021 11:16:38 +0300
From: Ido Schimmel <idosch@...sch.org>
To: Vladimir Oltean <vladimir.oltean@....com>, nikolay@...dia.com
Cc: netdev@...r.kernel.org, Ido Schimmel <idosch@...dia.com>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
Jiri Pirko <jiri@...dia.com>
Subject: Re: [PATCH net-next 6/8] net: bridge: move br_fdb_replay inside
br_switchdev.c
On Tue, Oct 26, 2021 at 05:27:41PM +0300, Vladimir Oltean wrote:
> br_fdb_replay is only called from switchdev code paths, so it makes
> sense to be disabled if switchdev is not enabled in the first place.
>
> As opposed to br_mdb_replay and br_vlan_replay which might be turned off
> depending on bridge support for multicast and VLANs, FDB support is
> always on. So moving br_mdb_replay and br_vlan_replay inside
> br_switchdev.c would mean adding some #ifdef's in br_switchdev.c, so we
> keep those where they are.
TBH, for consistency with br_mdb_replay() and br_vlan_replay(), it would
have been good to keep it where it is, but ...
>
> The reason for the movement is that in future changes there will be some
> code reuse between br_switchdev_fdb_notify and br_fdb_replay.
this seems like a good reason, so:
Reviewed-by: Ido Schimmel <idosch@...dia.com>
Nik, WDYT?
Powered by blists - more mailing lists