DPDK usage discussions
 help / color / mirror / Atom feed
From: Rohit Kumar <rokumar@idirect.net>
To: users@dpdk.org
Subject: net/mlx5: no RX with VLAN filter offload set
Date: Tue, 18 Oct 2022 10:56:45 +0200	[thread overview]
Message-ID: <149a0522-2052-ffe3-337d-852a7e1e6daa@idirect.net> (raw)
In-Reply-To: <dfeec6f2-54c2-a241-fa58-d78bf5bcc828@idirect.net>

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. Result from
dpdk 17.11 testing is also same. 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.

           reply	other threads:[~2022-10-24 15:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <dfeec6f2-54c2-a241-fa58-d78bf5bcc828@idirect.net>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=149a0522-2052-ffe3-337d-852a7e1e6daa@idirect.net \
    --to=rokumar@idirect.net \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).