[dpdk-dev] net/mlx5: no RX with VLAN filter offload (dpdk 19.11)

[dpdk-dev] net/mlx5: no RX with VLAN filter offload (dpdk 19.11)

[Rohit Kumar]

Hello,


DPDK: 19.11

Driver: mlx5

OS: CentOS Linux release 7.9.2009 (Kernel: 3.10.0-1160.66.1.el7.x86_64)

Iface: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function]

I am bringing-up our dpdk based L3 forwarding app in VM on Openshift
redhat platform. It has both RX and TX HW offloads enabled, including
VLAN filtering (DEV_RX_OFFLOAD_VLAN_FILTER). VLAN registers successfully
in the VF - however no packets are getting received in with the
registered VLAN. RX-packet counter doesn't increment and there are no
errors reported in stats, or even in logs with driver debug logging
enabled via log-level="mlx5,8".

Port ID 0 stats, rxPkts: 27, txPkts: 107, rxBytes: 1524, txBytes: 10366,
missed: 0, rxErrors: 0, txErrors: 0, rx_nombuf: 0
Port ID 0 stats, rxPkts: 27, txPkts: 112, rxBytes: 1524, txBytes: 10738,
missed: 0, rxErrors: 0, txErrors: 0, rx_nombuf: 0
Port ID 0 stats, rxPkts: 27, txPkts: 122, rxBytes: 1524, txBytes: 11410,
missed: 0, rxErrors: 0, txErrors: 0, rx_nombuf: 0

When no VLAN is registered or vlan filtering offload is disabled, then
IP unicast, broadcast and multicast packets are received, but no VLAN
packet, which means VLAN filtering offload doesn't work in 19.11
version. However filtering is working perfectly fine on the same setup
in dpdk 17.11 version. Result from l3fwd sample application is also
same. So I guess problem is in 19.11 version. Does anyone noticed or
reported such problem? Any help or pointer will be appreciated.


Thanks,
Rohit

This electronic message and any files transmitted with it contains information from ST Engineering iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.