All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1725] iavf pmd vlan Issue: dpdk-22.11.0
Date: Tue, 17 Jun 2025 06:35:01 +0000	[thread overview]
Message-ID: <bug-1725-3@https.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 3090 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1725

            Bug ID: 1725
           Summary: iavf pmd vlan Issue: dpdk-22.11.0
           Product: DPDK
           Version: 22.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: amiyaranjan.mohakud@gmail.com
  Target Milestone: ---

Hi All,

I'm encountering an issue with XL710 SR-IOV on KVM for VLAN packets with
DPDK-22.11.0 version. 

Issue Description: I have disabled RTE_ETH_RX_OFFLOAD_VLAN_STRIP in
rte_eth_conf and calling rte_eth_dev_configure and expecting my dpdk
application to receive the packets with vlan tags. Later I added some vlans
using rte_eth_dev_vlan_filter() and I see that the vlan is getting stripped off
 for the incoming packets. 

Setup Details:(KVM SR-IOV)

KVM Host: Ubuntu 20.04.6 LTS: kernel version: 5.4.0-216-generic #236-Ubuntu
NIC: XL710
3b:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for
40GbE QSFP+ (rev 02)
3b:00.1 Ethernet controller: Intel Corporation Ethernet Controller XL710 for
40GbE QSFP+ (rev 02)
i40e PF Driver: Out of tree 2.20.12
Firmware: 9.00/9.40 
DPDK Version: 22.11.0


Observation/Analysis:

I could see that even after disabling RTE_ETH_RX_OFFLOAD_VLAN_STRIP offload
flag, when I receive the packets, the mbuf offload flags (RTE_MBUF_F_RX_VLAN |
RTE_MBUF_F_RX_VLAN_STRIPPED) are set inside the mbuf. This confirms that the
driver is stripping off the vlans.


I tried with recommended PF driver version for DPDK-22.11.0 as per
https://mails.dpdk.org/archives/dev/2023-November/281700.html and DPDK-22.11
release note https://doc.dpdk.org/guides/rel_notes/release_22_11.html. Still it
did not help.


       Intel® Ethernet Converged Network Adapter XL710-QDA2 (2X40G)
    Firmware version(PF): 9.00 0x8000ce86 1.3179.0
    Device id (pf/vf): 8086:1583 / 8086:154c
    Driver version(out-tree): 2.20.12 (i40e)
    Driver version(in-tree): 5.15.0-46-generic (i40e)


Upon debugging further, I came across a DPDK commit:
https://github.com/DPDK/dpdk/commit/e25c7ed114b296ddaa583427824acc30bcf9c85d
which says it sets the vlan_strip on in PF when we set vlan filter on VF. 

I picked the fix, but still it did not help.

Later when I debugged further, I found that the vf_cap_flags is set to
VIRTCHNL_VF_OFFLOAD_VLAN_V2 for the above PF driver and still it sets the
vlan_strip on. I extended the dpdk commit for the VIRTCHNL_VF_OFFLOAD_VLAN_V2
case which fixed the issue.


I just want to know if it's a known issue for the VIRTCHNL_VF_OFFLOAD_VLAN_V2
case. I understand it's a known issue for VIRTCHNL_VF_OFFLOAD_VLAN_V1 and dpdk
has a fix for it. 
Do we need to add the fix for VIRTCHNL_VF_OFFLOAD_VLAN_V2 as well. Can we
mainstream it? If yes, please let me know so that I can raise a pull request
for it, if required.

Regards
Amiya

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 5189 bytes --]

             reply	other threads:[~2025-06-17  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  6:35 bugzilla [this message]
     [not found] <bug-1725-3@http.bugs.dpdk.org/>
2025-10-23 16:50 ` [DPDK/ethdev Bug 1725] iavf pmd vlan Issue: dpdk-22.11.0 bugzilla

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=bug-1725-3@https.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.