[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190222.115354.1384012175579493298.davem@davemloft.net>
Date: Fri, 22 Feb 2019 11:53:54 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: f.fainelli@...il.com
Cc: netdev@...r.kernel.org, andrew@...n.ch, vivien.didelot@...il.com,
idosch@...lanox.com, jiri@...lanox.com, rmk+kernel@...linux.org.uk
Subject: Re: [PATCH net-next 0/2] net: dsa: VLAN devices w/ filtering
From: Florian Fainelli <f.fainelli@...il.com>
Date: Wed, 20 Feb 2019 14:35:37 -0800
> This patch series supports having VLAN devices on top of DSA/switch
> ports while the switch has VLAN filtering globally turned on (as is the
> case with Broadcom switches). Whether the switch does global or per-port
> VLAN filtering, having VLAN entries for these VLAN devices is
> beneficial.
>
> We take care of a few possibly problematic cases:
>
> - adding a VLAN device while there is an existing VLAN entry created by
> a VLAN aware bridge. The entire bridge's VLAN database and not just
> the specific bridge port is being checked to be safe and conserative
>
> - adding a bridge VLAN entry when there is an existing VLAN device
> created is also not possible because that would lead to the bridge
> being able to manipulate the VLAN device's VID/attributes under its feet
>
> - enslaving a VLAN device into a VLAN aware bridge since that duplicates
> functionality already offered by the VLAN aware bridge
>
> Here are the different test cases that were run to exercise this:
...
Series applied, thanks Florian.
Powered by blists - more mailing lists