summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2018-06-26 12:05:32 +0300
committerDavid S. Miller <davem@davemloft.net>2018-06-26 12:05:32 +0300
commit651b4513bdd232e92320f409d0f211c556ba80a9 (patch)
treeb898c25f0f431fa0eef410e949eb868e98a09460 /tools/perf/scripts/python
parentfb223502ec0889444965f602f57b1f45f9e9845e (diff)
parent5b1e7f9ebd5653dc4cc026671ca07d8ab2419a99 (diff)
downloadlinux-651b4513bdd232e92320f409d0f211c556ba80a9.tar.xz
Merge branch 'mlxsw-Support-bridge-router-interfaces-with-non-default-VLAN'
Ido Schimmel says: ==================== mlxsw: Support bridge router interfaces with non-default VLAN Petr says: When traffic is inserted on a router interface associated with an 802.1q bridge, the VLAN that the traffic appears on is determined by PVID of the bridge device itself. However currently mlxsw always configures such traffic to be forwarded to VLAN 1, regardless of the bridge PVID. Fix the problem by modifying the FID-handling code to assign such traffic not to FID that corresponds to VLAN 1, but to a FID that corresponds to the configured PVID. Bail out if there is no PVID. This is implemented in patches #1 and #2. From that point on, also forbid any changes to bridge device PVID, because such changes would not be reflected. This is implemented in patches #3, #4 and #5. Finally in patch #6, introduce tests that use bridge as a routed interface, and test mlxsw in both the currently-supported scenario of using PVID 1, and the newly-supported one of using a custom PVID. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions