On 11/26/18 2:07 PM, Ivan Khoronzhuk wrote: > On Mon, Nov 26, 2018 at 12:57:20PM -0600, Grygorii Strashko wrote: >> >> >> On 11/26/18 10:26 AM, Ivan Khoronzhuk wrote: >>> On Sun, Nov 25, 2018 at 05:46:26PM -0600, Grygorii Strashko wrote: >>>> In dual_mac mode CPSW driver uses vid1 and vid2 by default to implement >>>> dual mac mode wich are used to configure pvids for each external ports. >>>> But, historicaly, it also adds vid0 to ALE table and sets "untag" bits for both >>>> ext. ports. As result, it's imposible to use priority tagged packets in >>>> dual mac mode. >>>> >>>> Hence, drop vid0 configuration in dual mac mode as it's not required for dual >>>> mac mode functionality and, this way, make it possible to use priority >>>> tagged packet in dual mac mode. >>> So, now it's enabled to be added via regular ndo. >>> I have similar change in mind, but was going to send it after >>> mcast/ucast, and - enabling same vlans patch... >>> >>> 2 things stopped me to add this: >>> >>> 1) Moving it to be enabled via regular call is Ok, but in dual mac mode >>> it causes overlaps, at least while vid deletion. So decided to wait till >>> same vlans series is applied. >> >> TI driver documentation mentions this restriction >> "While adding VLAN id to the eth interfaces, >> same VLAN id should not be added in both interfaces which will lead to VLAN >> forwarding and act as switch" > It's not accurate now. > This sw bug "acting like a switch" was fixed indirectly in LKML ). > And at least for upstream version, not TISDK, desc should be updated, > but better do this when it fixed completely and merged with TISDK. > > I know about this "written" restriction > (for tiSDK, and it's not TRM after all ...), > it can be avoided and it's partly avoided now ... I'd like to clarify point about supporting same VLANs in dual_mac mode, to avoid future misunderstanding, overall: it's *not* supported as adding same VLAN to both netdevices will cause unknown unicast packets leaking between interfaces and it can't be avoided - hw limitation. Regarding vid0 - current default configuration of CPSW considers vid0/priority tagged packets as - untagged and assigns pvid to any such ingress packet inside switch. Hence, P0 (Linux host) egress port never modifies packet contents - this behavior is not visible to Linux. (EN_VID0_MODE=0, P1_PASS_PRI_TAGGED=0) > > Also, for notice, while you add any of the vlans to any of > the ports, vlan0 is added to both of them.....restricted it or not. > Thanks to last changes in the driver it's not "acting like a switch" > The patch in question enables this in ndo, not me. > > #ip link add link eth0 name eth0.400 type vlan id 400 > [ 326.538989] 8021q: 802.1Q VLAN Support v1.8 > [ 326.543217] 8021q: adding VLAN 0 to HW filter on device eth0 > [ 326.554645] 8021q: adding VLAN 0 to HW filter on device eth1 > [ 326.572236] net eth0: Adding vlanid 400 to vlan filter > > I just propose to extend it later, when it's correct to do. > But if no harm (basically no harm, only if someone decides > to add vlan0 to both ports and then delete on one of them) > , at least you should take this into account. > -- regards, -grygorii
