From: Linus Walleij <linus.walleij@linaro.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 3/3] net: dsa: Add Vitesse VSC73xx DSA router driver
Date: Mon, 4 Mar 2019 13:26:20 +0100 [thread overview]
Message-ID: <CACRpkdY648MXapATdHWZ9299tVkmxLdK65eWS+4RPkunGTXJ5A@mail.gmail.com> (raw)
In-Reply-To: <CA+h21hr7+HX64XGHY-LCZXkLLk3dGxx8JnALHTc=+Phvx=LU0Q@mail.gmail.com>
Hi Vladimir,
On Mon, Mar 4, 2019 at 1:14 PM Vladimir Oltean <olteanv@gmail.com> wrote:
> I may be in error, but I don't think we have the same understanding of what
> VLAN filtering is. As far as I understand, no VLAN filtering means that
> hardware is required to not parse, push or pop VLAN tags in whatever frames
> it receives or sends (tagged or not). Conversely, VLAN filtering enabled means
> hardware is required to parse VLAN information and enforce port membership.
OK I get it now, I hope I don't forget it the next 5 minutes.
I think I have the wrong mental model about a whole lot of things
regarding VLANs.
> Now, this is orthogonal to forwarding, in a way. I believe that if you want
> to isolate two front-panel ports from other two front-panel ports (be they WAN
> or LAN), you would want to add them to different bridges (br0 and br1).
> But indeed forwarding domain can also be limited using VLAN. In this case a
> frame will be passed from one port to another based on a compound decision
> (L2 forwarding rules allow AND VLAN port membership domain allows). You would
> want to use VLAN when you want a single port to be a member of multiple
> domains, because you can't put a single netdevice (front-panel switch port)
> in multiple bridges.
> All I'm really saying is that I don't think that inside the port_bridge_join
> callback, configuring forwarding based on VLAN is a sane thing to do.
>
> I do see that neither vitesse-vsc73xx nor rtl8366 do implement the bridge
> membership callbacks, and as I don't happen to know nearly enough about DSA, I
> wonder at what moment in time does forwarding get activated between ports.
I think I should seriously look at other DSA drivers implementing this
because I think that is what I really want to achieve here.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-03-04 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 12:35 [PATCH 0/3] DSA driver for Vitesse VSC73xx Linus Walleij
2018-06-14 12:35 ` [PATCH 1/3] net: dsa: Add DT bindings for Vitesse VSC73xx switches Linus Walleij
2018-06-14 16:09 ` Florian Fainelli
2018-06-14 16:09 ` Florian Fainelli
2018-06-17 7:40 ` Jiri Pirko
2018-06-14 12:35 ` [PATCH 2/3] net: phy: vitesse: Add support for VSC73xx Linus Walleij
2018-06-14 16:29 ` Florian Fainelli
2018-06-15 19:24 ` Woojung.Huh
2018-06-28 18:23 ` Linus Walleij
2018-06-14 12:35 ` [PATCH 3/3] net: dsa: Add Vitesse VSC73xx DSA router driver Linus Walleij
2018-06-14 16:51 ` Florian Fainelli
2018-06-30 11:05 ` Linus Walleij
2018-06-30 11:05 ` Linus Walleij
2019-03-03 12:08 ` Vladimir Oltean
2019-03-04 9:51 ` Linus Walleij
2019-03-04 12:14 ` Vladimir Oltean
2019-03-04 12:26 ` Linus Walleij [this message]
2019-03-04 13:53 ` Andrew Lunn
2019-03-04 14:10 ` 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=CACRpkdY648MXapATdHWZ9299tVkmxLdK65eWS+4RPkunGTXJ5A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andrew@lunn.ch \
--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 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).