netdev - [PATCH net-next 0/4] Cross-chip bridging for disjoint DSA trees

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200429161952.17769-1-olteanv@gmail.com>
Date:   Wed, 29 Apr 2020 19:19:48 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     andrew@...n.ch, f.fainelli@...il.com, vivien.didelot@...il.com,
        davem@...emloft.net
Cc:     jiri@...nulli.us, idosch@...sch.org, kuba@...nel.org,
        netdev@...r.kernel.org, leoyang.li@....com,
        nikolay@...ulusnetworks.com
Subject: [PATCH net-next 0/4] Cross-chip bridging for disjoint DSA trees

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.

Florian Fainelli (1):
  bridge: Allow enslaving DSA master network devices

Vladimir Oltean (3):
  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_main.c | 122 +++++++++++++++++++++++++
 include/net/dsa.h                      |  11 ++-
 net/bridge/br_if.c                     |   4 +-
 net/bridge/br_input.c                  |   4 +-
 net/dsa/dsa2.c                         |  21 +++++
 net/dsa/dsa_priv.h                     |   1 +
 net/dsa/port.c                         |  23 ++++-
 net/dsa/switch.c                       |  21 +++--
 9 files changed, 203 insertions(+), 20 deletions(-)

-- 
2.17.1