aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/ice/ice_lib.c
diff options
context:
space:
mode:
authorAmit Cohen <[email protected]>2022-08-17 15:28:28 +0000
committerJakub Kicinski <[email protected]>2022-08-19 03:50:41 +0000
commit1623d5719fdff46620eb55c5d4f0cf8af1afcdb4 (patch)
tree5d12846be5357d8c3649a4977f2839a6f3b870cf /drivers/net/ethernet/intel/ice/ice_lib.c
parentselftests: mlxsw: Add ingress RIF configuration test for VXLAN (diff)
downloadkernel-1623d5719fdff46620eb55c5d4f0cf8af1afcdb4.tar.gz
kernel-1623d5719fdff46620eb55c5d4f0cf8af1afcdb4.zip
selftests: mlxsw: Add egress VID classification test
After routing, the device always consults a table that determines the packet's egress VID based on {egress RIF, egress local port}. In the unified bridge model, it is up to software to maintain this table via REIV register. The table needs to be updated in the following flows: 1. When a RIF is set on a FID, for each FID's {Port, VID} mapping, a new {RIF, Port}->VID mapping should be created. 2. When a {Port, VID} is mapped to a FID and the FID already has a RIF, a new {RIF, Port}->VID mapping should be created. Add a test to verify that packets get the correct VID after routing, regardless of the order of the configuration. # ./egress_vid_classification.sh TEST: Add RIF for existing {port, VID}->FID mapping [ OK ] TEST: Add {port, VID}->FID mapping for FID with a RIF [ OK ] Signed-off-by: Amit Cohen <[email protected]> Reviewed-by: Ido Schimmel <[email protected]> Signed-off-by: Petr Machata <[email protected]> Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_lib.c')
0 files changed, 0 insertions, 0 deletions