From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v2 9/9] net: dsa: mv88e6xxx: add cross-chip bridging
Date: Fri, 31 Mar 2017 18:39:49 +0200 [thread overview]
Message-ID: <20170331163949.GI12814@lunn.ch> (raw)
In-Reply-To: <20170330213715.9666-10-vivien.didelot@savoirfairelinux.com>
On Thu, Mar 30, 2017 at 05:37:15PM -0400, Vivien Didelot wrote:
> Implement the DSA cross-chip bridging operations by remapping the local
> ports an external source port can egress frames to, when this cross-chip
> port joins or leaves a bridge.
>
> The PVT is no longer configured with all ones allowing any external
> frame to egress any local port. Only DSA and CPU ports, as well as
> bridge group members, can egress frames on local ports.
Hi Vivien
With the ZII devel B, we have two switches with PVT, and one
without. What happens in this setup? Can the non-PVT switch leak
frames out user ports which should otherwise be blocked?
Thanks
Andrew
next prev parent reply other threads:[~2017-03-31 16:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 21:37 [PATCH net-next v2 0/9] net: dsa: mv88e6xxx: program cross-chip bridging Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 1/9] net: dsa: mv88e6xxx: move PVT description in info Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 2/9] net: dsa: mv88e6xxx: use 4-bit port for PVT data Vivien Didelot
2017-03-31 16:33 ` Andrew Lunn
2017-03-30 21:37 ` [PATCH net-next v2 3/9] net: dsa: mv88e6xxx: program the PVT with all ones Vivien Didelot
2017-03-31 16:35 ` Andrew Lunn
2017-03-30 21:37 ` [PATCH net-next v2 4/9] net: dsa: mv88e6xxx: allocate the number of ports Vivien Didelot
2017-03-31 16:27 ` Andrew Lunn
2017-03-30 21:37 ` [PATCH net-next v2 5/9] net: dsa: mv88e6xxx: rework in-chip bridging Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 6/9] net: dsa: mv88e6xxx: factorize in-chip bridge map Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 7/9] net: dsa: mv88e6xxx: remap existing bridge members Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 8/9] net: dsa: add cross-chip bridging operations Vivien Didelot
2017-03-30 21:37 ` [PATCH net-next v2 9/9] net: dsa: mv88e6xxx: add cross-chip bridging Vivien Didelot
2017-03-31 16:39 ` Andrew Lunn [this message]
2017-03-31 16:55 ` Vivien Didelot
2017-03-31 17:09 ` Andrew Lunn
2017-03-31 17:27 ` Vivien Didelot
2017-04-01 19:23 ` [PATCH net-next v2 0/9] net: dsa: mv88e6xxx: program " David Miller
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=20170331163949.GI12814@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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