From: David S. Miller Date: Thu, 10 May 2018 21:50:53 +0000 (-0400) Subject: Merge branch 'mlxsw-Support-VLAN-devices-in-mirroring-offloads' X-Git-Tag: v4.19~872^2~271 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ccb0263814149883e80a07ffad79dbd0690e3ba9;p=platform%2Fkernel%2Flinux-rpi.git Merge branch 'mlxsw-Support-VLAN-devices-in-mirroring-offloads' Ido Schimmel says: ==================== mlxsw: Support VLAN devices in mirroring offloads Petr says: When offloading "tc action mirred mirror", there are several scenarios where VLAN devices can show up, that mlxsw can offload on Spectrum machines. I) A direct mirror to a VLAN device on top of a front-panel port device (commonly referred to as "RSPAN") II) VLAN device in egress path of a packet when resolving a mirror to gretap or ip6gretap netdevice. Specifically in the latter case, the following are the cases that can be offloaded: IIa) VLAN device directly above a physical device. IIb) A VLAN-unaware bridge where the egress device is as in IIa. IIc) VLAN device on top of a VLAN-aware bridge where the egress device is a physical device. This patch set implements all the above cases. First, in patch #1, br_vlan_get_info() is extended to allow bridge master argument. Case I is then implemented in patches #2 and #3, case II in patch #4. Note that handling of VLAN protocol is not included. In case I, mirrored packets may end up being double-tagged, and it might be reasonable for the outer tag to be an 802.1ad. However, the protocol type configuration would have to be put on the same VLAN netdevice that represents normal VLAN traffic, and mlxsw currently ignores this setting in that case. Thus this support was left out and the encapsulation always uses 802.1q protocol. ==================== Signed-off-by: David S. Miller --- ccb0263814149883e80a07ffad79dbd0690e3ba9