From: Vladimir Oltean <olteanv@gmail.com>
To: Christian Eggers <ceggers@arri.de>
Cc: netdev@vger.kernel.org
Subject: Re: Using a bridge for DSA and non-DSA devices
Date: Mon, 5 Dec 2022 21:08:05 +0200 [thread overview]
Message-ID: <20221205190805.vwcv6z7ize3z64j2@skbuf> (raw)
In-Reply-To: <2269377.ElGaqSPkdT@n95hx1g2>
Hi Christian,
On Mon, Dec 05, 2022 at 07:15:42PM +0100, Christian Eggers wrote:
> Usually a bridge does forwarding of traffic between different hardware
> interfaces in software. For DSA, setting up a bridge configures the
> hardware in a way that traffic is forwarded in hardware.
>
> Is there any problem combining these two situations on a single bridge?
> Currently I use a bridge for configuring a DSA switch with two DSA slave
> interfaces. Can I add a non-DSA device (e.g. an USB Ethernet gadget)
> to this bridge?
In the model that the DSA core tries to impose, software bridging is
possible, as long as you understand the physical constraints (throughput
will be limited by the link speed of the CPU ports), and as long as the
switch doesn't use DSA_TAG_PROTO_NONE (a remnant of the past).
Unfortunately the results might depend on which switch driver you use
for this, since some driver cooperation is needed for smooth sailing,
and we don't see perfect uniformity. See the
ds->assisted_learning_on_cpu_port flag for some more details.
Did you already try to experiment with software bridging and faced any
issues?
next prev parent reply other threads:[~2022-12-05 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 18:15 Using a bridge for DSA and non-DSA devices Christian Eggers
2022-12-05 19:08 ` Vladimir Oltean [this message]
2022-12-05 20:08 ` Christian Eggers
2022-12-05 20:43 ` 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=20221205190805.vwcv6z7ize3z64j2@skbuf \
--to=olteanv@gmail.com \
--cc=ceggers@arri.de \
--cc=netdev@vger.kernel.org \
/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