There are some limitations on the some NICs (at least on ConnectX-6DX and BlueField2) with supporting FCS (frame checksum) scattering for the tunnel decapsulated packets.
For the case only one of the features can be supported in the same time, and the new devarg "decap_en" is introduced to provide the choice to the users. If FCS scattering feature is not supposed to be engaged by application, this new devarg should be specified as "decap_en=0", forcing the FCS feature enable and rejecting tunnel decap actions in the rte_flow engine. If FCS scatter is not needed and application supposes to use tunnel decapsulation in rte_flow, the devarg can be omitted or set to non-zero value (this is default settings). Suanming Mou (2): common/mlx5: add scatter FCS with decap capability query net/mlx5: add decap enable device argument doc/guides/nics/mlx5.rst | 15 +++++++++++++++ drivers/common/mlx5/mlx5_devx_cmds.c | 2 ++ drivers/common/mlx5/mlx5_devx_cmds.h | 1 + drivers/common/mlx5/mlx5_prm.h | 4 +++- drivers/net/mlx5/linux/mlx5_os.c | 12 ++++++++++-- drivers/net/mlx5/mlx5.c | 6 ++++++ drivers/net/mlx5/mlx5.h | 1 + drivers/net/mlx5/mlx5_flow_dv.c | 5 +++++ 8 files changed, 43 insertions(+), 3 deletions(-) -- 1.8.3.1
