Offload software learnt bridge addresses to DSA
Status from this message: This series was applied to netdev/net-next.git (refs/heads/master):
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest7 patches 2 repliesApplied 7/7
- v1 RFC3 patches 19 repliesSuperseded
Patches in v4 All 7 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | net: bridge: notify switchdev of disappearance of old FDB entry upon migrationnet/ | +1 | 1 reply | Applied |
| 2/7 | net: dsa: be louder when a non-legacy FDB operation failsnet/ | +7 | 1 reply | Applied |
| 3/7 | net: dsa: don't use switchdev_notifier_fdb_info in dsa_switchdev_event_worknet/ net/ | +65 | 0 replies | Applied |
| 4/7 | net: dsa: move switchdev event implementation under the same switch/case statementnet/ | +16 | 0 replies | Applied |
| 5/7 | net: dsa: exit early in dsa_slave_switchdev_event if we can't program the FDBnet/ | +3 | 0 replies | Applied |
| 6/7 | net: dsa: listen for SWITCHDEV_{FDB,DEL}_ADD_TO_DEVICE on foreign bridge neighborsinclude/ net/ | +60 | 0 replies | Applied |
| 7/7 | net: dsa: ocelot: request DSA to fix up lack of address learning on CPU portdrivers/ | +1 | 0 replies | Applied |
Reviews trailers per patch
All 7 patches have a Reviewed-by or Acked-by.
| Patch | Nikolay Aleksandrov | Ido Schimmel | Andrew Lunn | Florian Fainelli |
|---|---|---|---|---|
| 1/7 | A-b | R-b | R-b | R-b |
| 2/7 | R-b | R-b | ||
| 3/7 | R-b | |||
| 4/7 | R-b | |||
| 5/7 | R-b | R-b | ||
| 6/7 | R-b | R-b | ||
| 7/7 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 4 reviewers.
Cover letter [PATCH v4 net-next 0/7] Offload software learnt bridge addresses to DSA
From: Vladimir Oltean <[email protected]>
This series tries to make DSA behave a bit more sanely when bridged with "foreign" (non-DSA) interfaces and source address learning is not supported on the hardware CPU port (which would make things work more seamlessly without software intervention). When a station A connected to a DSA switch port needs to talk to another station B connected to a non-DSA port through the Linux bridge, DSA must explicitly add a route for station B towards its CPU port.
Initial RFC was posted here:
https://patchwork.ozlabs.org/project/netdev/cover/[email protected]/
v2 was posted here:
https://patchwork.kernel.org/project/netdevbpf/cover/[email protected]/
v3 was posted here:
https://patchwork.kernel.org/project/netdevbpf/cover/[email protected]/
This is a resend of the previous v3 with some added Reviewed-by tags.
Vladimir Oltean (7):
net: bridge: notify switchdev of disappearance of old FDB entry upon
migration
net: dsa: be louder when a non-legacy FDB operation fails
net: dsa: don't use switchdev_notifier_fdb_info in
dsa_switchdev_event_work
net: dsa: move switchdev event implementation under the same
switch/case statement
net: dsa: exit early in dsa_slave_switchdev_event if we can't program
the FDB
net: dsa: listen for SWITCHDEV_{FDB,DEL}_ADD_TO_DEVICE on foreign
bridge neighbors
net: dsa: ocelot: request DSA to fix up lack of address learning on
CPU port
drivers/net/dsa/ocelot/felix.c | 1 + include/net/dsa.h | 5 + net/bridge/br_fdb.c | 1 + net/dsa/dsa_priv.h | 12 +++ net/dsa/slave.c | 174 +++++++++++++++++++++------------ 5 files changed, 130 insertions(+), 63 deletions(-)
Signature · 1 line
2.25.1