From: "Deng, KaiwenX" <kaiwenx.deng@intel.com>
To: Amiya Ranjan Mohakud <amiya-ranjan.mohakud@broadcom.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
Subject: RE: Regarding https://mails.dpdk.org/archives/dev/2023-June/270558.html dpdk patch
Date: Thu, 25 Jan 2024 06:10:28 +0000 [thread overview]
Message-ID: <DS7PR11MB7860C835193ECB935052D75E8E7A2@DS7PR11MB7860.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJgakAdETfSvaPym+-LERemydH5UmBLR2R5VzvmMQjP=A301+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]
Hi Amiya
Can you provide me with the DPDK startup parameters?
Thanks
From: Amiya Ranjan Mohakud <amiya-ranjan.mohakud@broadcom.com>
Sent: Tuesday, January 23, 2024 4:54 PM
To: Deng, KaiwenX <kaiwenx.deng@intel.com>; dev@dpdk.org
Cc: Amiya Ranjan Mohakud <amiya-ranjan.mohakud@broadcom.com>; Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
Subject: Regarding https://mails.dpdk.org/archives/dev/2023-June/270558.html dpdk patch
Hi Kaiwenx
I came across the below DPDK iavf error message during the initialization of X710 NICs in ESX. It seems the functionality works fine, but with below error messages.
DPDK Version: 22.11.2
2023-12-08T09:58:00.901 |9322| MSG [NET] dpdk_port_configure:1717 Configure port eth3/1. lsc_intr=1, rxq/txq=1/1, (rss_enabled=1) rss_hf=0x0000000000000c30 tx_ol=0x00000000000006 rx_ol=0x00000000080007
2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_execute_vf_cmd(): Return failure -4 for cmd 27
2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_enable_vlan_strip(): Failed to execute command of OP_ENABLE_VLAN_STRIPPING
2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_dev_init_vlan(): Failed to update vlan offload
2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_dev_configure(): configure VLAN failed: -5
2023-12-08T09:58:01.156 |9322| MSG [NET] dpdk_log_write:107 iavf_execute_vf_cmd(): Return failure -5 for cmd 14
On search, I came across your above patch. I am not able to make out properly from the description. Could you please help elaborate the root cause/fix for my understanding and kindly confirm if this patch would fix the above issue. Thanks in advance.
Regards,
Amiya
This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
[-- Attachment #2: Type: text/html, Size: 7644 bytes --]
next prev parent reply other threads:[~2024-01-25 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 8:53 Amiya Ranjan Mohakud
2024-01-25 6:10 ` Deng, KaiwenX [this message]
2024-02-05 11:08 ` Amiya Ranjan Mohakud
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=DS7PR11MB7860C835193ECB935052D75E8E7A2@DS7PR11MB7860.namprd11.prod.outlook.com \
--to=kaiwenx.deng@intel.com \
--cc=amiya-ranjan.mohakud@broadcom.com \
--cc=amiyaranjan.mohakud@gmail.com \
--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 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).