[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210728182748.3564726-1-vladimir.oltean@nxp.com>
Date: Wed, 28 Jul 2021 21:27:46 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Ido Schimmel <idosch@...dia.com>, Jiri Pirko <jiri@...dia.com>,
Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
Tobias Waldekranz <tobias@...dekranz.com>
Subject: [PATCH net-next 0/2] Plug the last 2 holes in the switchdev notifiers for local FDB entries
The work for trapping local FDB entries to the CPU in switchdev/DSA
started with the "RX filtering in DSA" series:
https://patchwork.kernel.org/project/netdevbpf/cover/20210629140658.2510288-1-olteanv@gmail.com/
and was continued with further improvements such as "Fan out FDB entries
pointing towards the bridge to all switchdev member ports":
https://patchwork.kernel.org/project/netdevbpf/cover/20210719135140.278938-1-vladimir.oltean@nxp.com/
https://patchwork.kernel.org/project/netdevbpf/cover/20210720173557.999534-1-vladimir.oltean@nxp.com/
There are only 2 more issues left to be addressed (famous last words),
and these are:
- dynamically learned FDB entries towards interfaces foreign to DSA need
to be replayed too
- adding/deleting a VLAN on a port causes the local FDB entries in that
VLAN to be prematurely deleted
This patch series addresses both, and patch 2 depends on 1 to work properly.
Vladimir Oltean (2):
net: bridge: switchdev: replay the entire FDB for each port
net: bridge: switchdev: treat local FDBs the same as entries towards
the bridge
net/bridge/br_fdb.c | 24 +++++++-----------------
net/bridge/br_private.h | 4 ++--
net/bridge/br_switchdev.c | 16 +++-------------
3 files changed, 12 insertions(+), 32 deletions(-)
--
2.25.1
Powered by blists - more mailing lists