Re: [net-next 16/17] net/mlx5: Bridge, allow merged eswitch connectivity

On Mon, 16 Aug 2021 14:18:46 -0700 Saeed Mahameed wrote:

From: Vlad Buslov <redacted>

Allow connectivity between representors of different eswitch instances that
are attached to same bridge when merged_eswitch capability is enabled. Add
ports of peer eswitch to bridge instance and mark them with
MLX5_ESW_BRIDGE_PORT_FLAG_PEER. Mark FDBs offloaded on peer ports with
MLX5_ESW_BRIDGE_FLAG_PEER flag. Such FDBs can only be aged out on their
local eswitch instance, which then sends SWITCHDEV_FDB_DEL_TO_BRIDGE event.
Listen to the event on mlx5 bridge implementation and delete peer FDBs in
event handler.

Signed-off-by: Vlad Buslov <redacted>
Reviewed-by: Roi Dayan <redacted>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

drivers/net/ethernet/mellanox/mlx5/core/en/rep/bridge.c: In function ‘mlx5_esw_bridge_switchdev_fdb_event_work’:
drivers/net/ethernet/mellanox/mlx5/core/en/rep/bridge.c:286:21: warning: variable ‘priv’ set but not used [-Wunused-but-set-variable]
  286 |  struct mlx5e_priv *priv;
      |                     ^~~~