From: Andrew Lunn <andrew@lunn.ch>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
netdev@vger.kernel.org
Subject: Re: Crosschip bridge functionality
Date: Sat, 24 Dec 2022 00:03:03 +0100 [thread overview]
Message-ID: <Y6Yzp84WW1tQLdsB@lunn.ch> (raw)
In-Reply-To: <Y6YtiwqJWyv3yW9r@euler>
> Fair question. We have a baseboard configuration with cards that offer
> customization / expansion. An example might be a card that offers
> additional fibre / copper ports, which would lend itself very nicely to
> a DSA configuration... more cards == more ports.
>
> We can see some interesting use of vlans for all sorts of things. I
> haven't been the boots on the ground, so I don't know all the use-cases.
> My main hope is to be able to offer as much configurability for the
> system integrators as possible. Maybe sw2p2 is a tap of sw1p2, while
> sw2p3, sw2p4, and sw1p3 are bridged, with the CPU doing IGMP snooping
> and running RSTP.
>
> >
> > I know people have stacked switches before, and just operated them as
> > stacked switches. So you need to configure each switch independently.
> > What Marvell DSA does is make it transparent, so to some extent it
> > looks like one big switch, not a collection of switches.
>
> That is definitely possible. It might make the people doing any system
> integration have a lot more knowledge than a simple "add this port to
> that bridge". My goal is to make their lives as easy as can be.
>
> It sounds like that all exists with Marvell hardware...
You might want get hold of a Turris Mox system, with a few different
cards in it. That will give you a Marvell D in DSA system to play
with. And your system seems quite similar in some ways.
Andrew
next prev parent reply other threads:[~2022-12-23 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 19:37 Crosschip bridge functionality Colin Foster
2022-12-23 20:05 ` Andrew Lunn
2022-12-23 20:54 ` Colin Foster
2022-12-23 21:18 ` Andrew Lunn
2022-12-23 22:36 ` Colin Foster
2022-12-23 23:03 ` Andrew Lunn [this message]
2022-12-23 23:31 ` Colin Foster
2022-12-24 0:59 ` Vladimir Oltean
2022-12-24 18:53 ` Colin Foster
2023-01-03 10:47 ` Vladimir Oltean
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=Y6Yzp84WW1tQLdsB@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.belloni@bootlin.com \
--cc=colin.foster@in-advantage.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.