Skip to content

selftests: mlxsw: Add ordering tests for unified bridge model

Petr Machata netdev 1 version Applied

Status from this message: This series was applied to netdev/net-next.git (master)

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 0 repliesApplied 4/4

Patches in v1 All 4 applied

#Subject and filesSizeRepliesApplied
1/4selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridgetools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh+264 -00 repliesApplied
2/4selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridgetools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1q.sh+264 -00 repliesApplied
3/4selftests: mlxsw: Add ingress RIF configuration test for VXLANtools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_vxlan.sh+311 -00 repliesApplied
4/4selftests: mlxsw: Add egress VID classification testtools/testing/selftests/drivers/net/mlxsw/egress_vid_classification.sh+273 -00 repliesApplied

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by.

PatchIdo Schimmel
1/4R-b
2/4R-b
3/4R-b
4/4R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model

Amit Cohen writes:

Commit 798661c73672 ("Merge branch 'mlxsw-unified-bridge-conversion-part-6'") converted mlxsw driver to use unified bridge model. In the legacy model, when a RIF was created / destroyed, it was firmware's responsibility to update it in the relevant FID classification records. In the unified bridge model, this responsibility moved to software.

This set adds tests to check the order of configuration for the following classifications:
1. {Port, VID} -> FID
2. VID -> FID
3. VNI -> FID (after decapsulation)

In addition, in the legacy model, software is responsible to update a table which is used to determine the packet's egress VID. Add a test to check that the order of configuration does not impact switch behavior.

See more details in the commit messages.

Note that the tests supposed to pass also using the legacy model, they are added now as with the new model they test the driver and not the firmware.

Patch set overview:
Patch #1 adds test for {Port, VID} -> FID
Patch #2 adds test for VID -> FID
Patch #3 adds test for VNI -> FID
Patch #4 adds test for egress VID classification

Amit Cohen (4):
selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge
selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge
selftests: mlxsw: Add ingress RIF configuration test for VXLAN
selftests: mlxsw: Add egress VID classification test

 .../net/mlxsw/egress_vid_classification.sh    | 273 +++++++++++++++
 .../drivers/net/mlxsw/ingress_rif_conf_1d.sh  | 264 +++++++++++++++
 .../drivers/net/mlxsw/ingress_rif_conf_1q.sh  | 264 +++++++++++++++
 .../net/mlxsw/ingress_rif_conf_vxlan.sh       | 311 ++++++++++++++++++
 4 files changed, 1112 insertions(+)
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/egress_vid_classification.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1q.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_vxlan.sh
Signature · 1 line
2.35.3