From: Florian Fainelli <f.fainelli@gmail.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next 5/5] net: dsa: mv88e6xxx: do not purge a VTU entry
Date: Wed, 7 Jun 2017 12:37:37 -0700 [thread overview]
Message-ID: <ae09e920-fcea-ac29-3b2d-51275e0fec56@gmail.com> (raw)
In-Reply-To: <20170606205631.22880-6-vivien.didelot@savoirfairelinux.com>
On 06/06/2017 01:56 PM, Vivien Didelot wrote:
> The mv88e6xxx driver currently tries to be smart and remove by itself a
> VLAN entry from the VTU when the driven switch sees no user ports as
> members of the VLAN.
>
> This is bad in a multi-chip switch fabric, since a chip in between
> others may have no bridge port members, but still needs to be aware of
> the VID in order to correctly pass frames in the data path.
>
> Remove the code purging a VTU entry when updating a port membership.
In that case the switch sitting between two other chips and passing
traffic would still have at least two of its DSA ports be part of a VTU
entry, right?
So could not we just do ....
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> ---
> drivers/net/dsa/mv88e6xxx/chip.c | 15 +--------------
> 1 file changed, 1 insertion(+), 14 deletions(-)
>
> diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
> index 522f023bb17e..64c0f88f9e79 100644
> --- a/drivers/net/dsa/mv88e6xxx/chip.c
> +++ b/drivers/net/dsa/mv88e6xxx/chip.c
> @@ -1325,9 +1325,8 @@ static void mv88e6xxx_port_vlan_add(struct dsa_switch *ds, int port,
> static int _mv88e6xxx_port_vlan_del(struct mv88e6xxx_chip *chip,
> int port, u16 vid)
> {
> - struct dsa_switch *ds = chip->ds;
> struct mv88e6xxx_vtu_entry vlan;
> - int i, err;
> + int err;
>
> err = mv88e6xxx_vtu_get(chip, vid, &vlan, false);
> if (err)
> @@ -1339,18 +1338,6 @@ static int _mv88e6xxx_port_vlan_del(struct mv88e6xxx_chip *chip,
>
> vlan.member[port] = GLOBAL_VTU_DATA_MEMBER_TAG_NON_MEMBER;
>
> - /* keep the VLAN unless all ports are excluded */
> - vlan.valid = false;
> - for (i = 0; i < mv88e6xxx_num_ports(chip); ++i) {
> - if (dsa_is_cpu_port(ds, i) || dsa_is_dsa_port(ds, i))
> - continue;
... break the loop here?
> -
> - if (vlan.member[i] != GLOBAL_VTU_DATA_MEMBER_TAG_NON_MEMBER) {
> - vlan.valid = true;
> - break;
> - }
> - }
> -
> err = mv88e6xxx_vtu_loadpurge(chip, &vlan);
> if (err)
> return err;
>
--
Florian
next prev parent reply other threads:[~2017-06-07 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 20:56 [PATCH net-next 0/5] net: dsa: add cross-chip VLAN support Vivien Didelot
2017-06-06 20:56 ` [PATCH net-next 1/5] net: dsa: mv88e6xxx: define membership on VLAN add Vivien Didelot
2017-06-07 19:31 ` Florian Fainelli
2017-06-06 20:56 ` [PATCH net-next 2/5] net: dsa: check VLAN capability of every switch Vivien Didelot
2017-06-07 19:39 ` Florian Fainelli
2017-06-07 20:03 ` Vivien Didelot
2017-06-06 20:56 ` [PATCH net-next 3/5] net: dsa: add CPU and DSA ports as VLAN members Vivien Didelot
2017-06-07 19:00 ` David Miller
2017-06-07 19:38 ` Florian Fainelli
2017-06-06 20:56 ` [PATCH net-next 4/5] net: dsa: mv88e6xxx: exclude all ports in new VLAN Vivien Didelot
2017-06-07 19:34 ` Florian Fainelli
2017-06-06 20:56 ` [PATCH net-next 5/5] net: dsa: mv88e6xxx: do not purge a VTU entry Vivien Didelot
2017-06-07 19:37 ` Florian Fainelli [this message]
2017-06-07 19:59 ` Vivien Didelot
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=ae09e920-fcea-ac29-3b2d-51275e0fec56@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).