Cross-chip bridging for disjoint DSA trees
Status from this message: Applied, thanks everyone!
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest4 patches 1 replyApplied
- v34 patches 8 repliesSuperseded
- v24 patches 3 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 4 patches | 7 replies | Superseded |
Patches in v4 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | net: bridge: allow enslaving some DSA master network devicesinclude/ net/ net/ +1 more | +49 | 0 replies | |
| 2/4 | net: dsa: permit cross-chip bridging between all trees in the systemdrivers/ include/ net/ +2 more | +55 | 0 replies | |
| 3/4 | net: dsa: introduce a dsa_switch_find functioninclude/ net/ | +22 | 0 replies | |
| 4/4 | net: dsa: sja1105: implement cross-chip bridging operationsdrivers/ drivers/ include/ +1 more | +288 | 0 replies |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by.
| Patch | Nikolay Aleksandrov | Florian Fainelli |
|---|---|---|
| 1/4 | A-b | R-b T-b |
| 2/4 | R-b | |
| 3/4 | R-b | |
| 4/4 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v4 resend net-next 0/4] Cross-chip bridging for disjoint DSA trees
From: Vladimir Oltean <[email protected]>
This series adds support for boards where DSA switches of multiple types are cascaded together. Actually this type of setup was brought up before on netdev, and it looks like utilizing disjoint trees is the way to go:
https://lkml.org/lkml/2019/7/7/225
The trouble with disjoint trees (prior to this patch series) is that only bridging of ports within the same hardware switch can be offloaded. After scratching my head for a while, it looks like the easiest way to support hardware bridging between different DSA trees is to bridge their DSA masters and extend the crosschip bridging operations.
I have given some thought to bridging the DSA masters with the slaves themselves, but given the hardware topology described in the commit message of patch 4/4, virtually any number (and combination) of bridges (forwarding domains) can be created on top of those 3x4-port front-panel switches. So it becomes a lot less obvious, when the front-panel ports are enslaved to more than 1 bridge, which bridge should the DSA masters be enslaved to.
So the least awkward approach was to just create a completely separate bridge for the DSA masters, whose entire purpose is to permit hardware forwarding between the discrete switches beneath it.
This is a direct resend of v3, which was deferred due to lack of review. In the meantime Florian has reviewed and tested some of them.
v1 was submitted here:
https://patchwork.ozlabs.org/project/netdev/cover/[email protected]/
v2 was submitted here:
https://patchwork.ozlabs.org/project/netdev/cover/[email protected]/
v3 was submitted here:
https://patchwork.ozlabs.org/project/netdev/cover/[email protected]/
Vladimir Oltean (4):
net: bridge: allow enslaving some DSA master network devices
net: dsa: permit cross-chip bridging between all trees in the system
net: dsa: introduce a dsa_switch_find function
net: dsa: sja1105: implement cross-chip bridging operations
drivers/net/dsa/mv88e6xxx/chip.c | 16 ++- drivers/net/dsa/sja1105/sja1105.h | 2 + drivers/net/dsa/sja1105/sja1105_main.c | 90 +++++++++++++++ include/linux/dsa/8021q.h | 45 ++++++++ include/net/dsa.h | 13 ++- net/bridge/br_if.c | 32 ++++-- net/bridge/br_input.c | 23 +++- net/bridge/br_private.h | 6 +- net/dsa/dsa2.c | 21 ++++ net/dsa/dsa_priv.h | 1 + net/dsa/port.c | 23 +++- net/dsa/switch.c | 21 +++- net/dsa/tag_8021q.c | 151 +++++++++++++++++++++++++ 13 files changed, 414 insertions(+), 30 deletions(-)
Signature · 1 line
2.17.1