DPDK patches and discussions
 help / color / mirror / Atom feed
From: Amiya Ranjan Mohakud <amiya-ranjan.mohakud@broadcom.com>
To: "Deng, KaiwenX" <kaiwenx.deng@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
Subject: Re: Regarding https://mails.dpdk.org/archives/dev/2023-June/270558.html dpdk patch
Date: Mon, 5 Feb 2024 16:38:27 +0530	[thread overview]
Message-ID: <CAJgakAcckfsPSzrNsCvCxFXFEE3u5Gajb3CYRv-cB9s7Yj-uKA@mail.gmail.com> (raw)
In-Reply-To: <DS7PR11MB7860C835193ECB935052D75E8E7A2@DS7PR11MB7860.namprd11.prod.outlook.com>

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

Hi Kaiwenx,

There are no specific parameters except "-m 1024 -l 1,2".  Just that the
guest has 2 SR IOV X710 interfaces.

Just for an additional update -

ESX version: 8.0 U1
i40e PF driver version: 1.11.3.5
Firmware version:7.10 0x800075da 19.5.12

I tried updating the firmware version to 9.00 0x8000cadc 21.5.9 based on
the compatibility matrix
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=37976
But It still did not help.


I'm not sure if we need to upgrade the driver version as well. Please let
me know if you have any breakthroughs. Thanks in advance.


Regards,
Amiya


On Thu, Jan 25, 2024 at 11:40 AM Deng, KaiwenX <kaiwenx.deng@intel.com>
wrote:

> 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.
>

-- 
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: 9670 bytes --]

      reply	other threads:[~2024-02-05 13:37 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
2024-02-05 11:08   ` Amiya Ranjan Mohakud [this message]

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=CAJgakAcckfsPSzrNsCvCxFXFEE3u5Gajb3CYRv-cB9s7Yj-uKA@mail.gmail.com \
    --to=amiya-ranjan.mohakud@broadcom.com \
    --cc=amiyaranjan.mohakud@gmail.com \
    --cc=dev@dpdk.org \
    --cc=kaiwenx.deng@intel.com \
    /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).