Re: [PATCH net-next v2] net: dsa: Support bridge 802.1Q while untagging

2020-10-01 Thread Vladimir Oltean
On Thu, Oct 01, 2020 at 04:48:43PM -0700, Florian Fainelli wrote: > > - move dsa_untag_bridge_pvid() after eth_type_trans(), similar to what > >you did in your initial patch - maybe this is the cleanest > > This would be my preference and it would not be hurting the fast-path that > much. Ok,

Re: [PATCH net-next v2] net: dsa: Support bridge 802.1Q while untagging

2020-10-01 Thread Florian Fainelli
On 10/1/2020 4:24 PM, Vladimir Oltean wrote: On Wed, Sep 30, 2020 at 08:06:23PM -0700, Florian Fainelli wrote: The intent of 412a1526d067 ("net: dsa: untag the bridge pvid from rx skbs") is to transparently untag the bridge's default_pvid when the Ethernet switch can only support egress tagge

Re: [PATCH net-next v2] net: dsa: Support bridge 802.1Q while untagging

2020-10-01 Thread Vladimir Oltean
On Fri, Oct 02, 2020 at 02:24:02AM +0300, Vladimir Oltean wrote: > The explanation is super confusing, although I think the placement of > the "skb->vlan_proto = vlan_dev_vlan_proto(upper_dev)" is correct. No, I think it _is_ wrong, after all, I think you're repairing skb->vlan_proto only for that

Re: [PATCH net-next v2] net: dsa: Support bridge 802.1Q while untagging

2020-10-01 Thread Vladimir Oltean
On Wed, Sep 30, 2020 at 08:06:23PM -0700, Florian Fainelli wrote: > The intent of 412a1526d067 ("net: dsa: untag the bridge pvid from rx > skbs") is to transparently untag the bridge's default_pvid when the > Ethernet switch can only support egress tagged of that default_pvid > towards the CPU port

[PATCH net-next v2] net: dsa: Support bridge 802.1Q while untagging

2020-09-30 Thread Florian Fainelli
The intent of 412a1526d067 ("net: dsa: untag the bridge pvid from rx skbs") is to transparently untag the bridge's default_pvid when the Ethernet switch can only support egress tagged of that default_pvid towards the CPU port. Prior to this commit, users would have to configure an 802.1Q upper on