From: Vladimir Oltean <olteanv@gmail.com>
To: andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
davem@davemloft.net
Cc: jiri@resnulli.us, idosch@idosch.org, kuba@kernel.org,
netdev@vger.kernel.org, nikolay@cumulusnetworks.com,
roopa@cumulusnetworks.com
Subject: [PATCH v4 resend net-next 0/4] Cross-chip bridging for disjoint DSA trees
Date: Sun, 10 May 2020 19:37:39 +0300 [thread overview]
Message-ID: <20200510163743.18032-1-olteanv@gmail.com> (raw)
From: Vladimir Oltean <vladimir.oltean@nxp.com>
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/20200429161952.17769-1-olteanv@gmail.com/
v2 was submitted here:
https://patchwork.ozlabs.org/project/netdev/cover/20200430202542.11797-1-olteanv@gmail.com/
v3 was submitted here:
https://patchwork.ozlabs.org/project/netdev/cover/20200503221228.10928-1-olteanv@gmail.com/
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(-)
--
2.17.1
next reply other threads:[~2020-05-10 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 16:37 Vladimir Oltean [this message]
2020-05-10 16:37 ` [PATCH v4 resend net-next 1/4] net: bridge: allow enslaving some DSA master network devices Vladimir Oltean
2020-05-10 16:37 ` [PATCH v4 resend net-next 2/4] net: dsa: permit cross-chip bridging between all trees in the system Vladimir Oltean
2020-05-10 16:37 ` [PATCH v4 resend net-next 3/4] net: dsa: introduce a dsa_switch_find function Vladimir Oltean
2020-05-10 16:37 ` [PATCH v4 resend net-next 4/4] net: dsa: sja1105: implement cross-chip bridging operations Vladimir Oltean
2020-05-11 2:56 ` [PATCH v4 resend net-next 0/4] Cross-chip bridging for disjoint DSA trees Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200510163743.18032-1-olteanv@gmail.com \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).