From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A027B43A96; Tue, 6 Feb 2024 14:08:26 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8DD0C4025E; Tue, 6 Feb 2024 14:08:26 +0100 (CET) Received: from mail-io1-f53.google.com (mail-io1-f53.google.com [209.85.166.53]) by mails.dpdk.org (Postfix) with ESMTP id 7C3904021E for ; Tue, 6 Feb 2024 13:43:58 +0100 (CET) Received: by mail-io1-f53.google.com with SMTP id ca18e2360f4ac-7bed9c7d33fso240561039f.1 for ; Tue, 06 Feb 2024 04:43:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1707223438; x=1707828238; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DXb7Kp7I0xBOpUo/PzDl9X0aYe3v3Aawaw8tjz7PknY=; b=g8PEoZf+6YsR2xHdGeMa+c7DQdL+MxkR/qDNWyDB0fd5nDoOdt9ib09Thb52j0Sgm6 e5Lqly/0HybbXGgPh5dUr6Z/nwy7rHzm0w9KnOt4dfqdGE/np7stVcUDuZoGuVCRAJSv vHX0lG+Dr2wWExAzsqU0juBuLBzPelprmwTM0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707223438; x=1707828238; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DXb7Kp7I0xBOpUo/PzDl9X0aYe3v3Aawaw8tjz7PknY=; b=Lk0tLEpDYi2RSQf9yPL2weMCL4KnZNnKRCCbNeEsnuWdtKYwvf0sQE05PTPWG/V19n RNRv3XZyul1kpoqCOY8PO7y15uzkko09ZbvuPLoURTfS3Dc26kfOVLCmZwVQB2RJ2Gn0 bg24GX5svdTuPtW8YffWv1eB+gCzfqoqZ1fRsijysIOBWyJY4jPyd01vYrv8FVTQNi1t RtO1MnAdNO6A6zXIo5zOZPq4LHx1R55b1GFjvdREgcHrvyLIEqTXMh4M7UoghmGmEqzb gcuMJ9MW4UULOc9q5itRnm5fnz35Bwf943iGpS5dNPS/T2h/n4Nlel2gKscf2TuxkJGX QxpA== X-Gm-Message-State: AOJu0Yxk/Me4TYaKsXu2S7BPf9Yf+DdmSzQMnPYzmGEdCMpEqGp+i1Rn gT+NIdRUi/yNNktSgBSgoRCrz+Lnj1HJLV5oG8nsiNcfC7WT9ienAUL+4TjxMG1oX/xqXOYZGLg JDL0E6MzfupqWl2WyUaeZnwN982PU4RyQvRHx4bjvce1faGs9wpiX1jiBkZzSEopOmhoKFwwAlO +3BXk1 X-Google-Smtp-Source: AGHT+IG5srhHiCDZ+w952Z1DUlljkzQicq4rwkxmZCKnoaW0nYqxej4YBdRL8qtbOeKX3rMkh/hgb/0B1K1itu6ayGA= X-Received: by 2002:a05:6602:256d:b0:7c3:e8ea:cb2b with SMTP id dj13-20020a056602256d00b007c3e8eacb2bmr2784031iob.8.1707223437731; Tue, 06 Feb 2024 04:43:57 -0800 (PST) MIME-Version: 1.0 References: <20240206095607.339410-1-david.marchand@redhat.com> <20240206103420.341328-1-david.marchand@redhat.com> In-Reply-To: <20240206103420.341328-1-david.marchand@redhat.com> From: Amiya Ranjan Mohakud Date: Tue, 6 Feb 2024 18:13:21 +0530 Message-ID: Subject: Re: [PATCH v2] net/iavf: remove error logs for vlan offloading To: David Marchand Cc: dev@dpdk.org, bruce.richardson@intel.com, stable@dpdk.org, Jingjing Wu , Qiming Yang , Qi Zhang , Haiyue Wang Content-Type: multipart/mixed; boundary="0000000000008f367b0610b5ee97" X-Mailman-Approved-At: Tue, 06 Feb 2024 14:08:25 +0100 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000008f367b0610b5ee97 Content-Type: multipart/alternative; boundary="0000000000008f36790610b5ee95" --0000000000008f36790610b5ee95 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi David, Thanks for the patch. I also see a similar error with iavf using dpdk-22.11.1. But in my case, I see 2 more additional error logs showing up during iavf_dev_configure(). It's with ESX-8.0U1 with an inbox driver. Firmware upgrade did not resolve the issue though. 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 I was currently following up with KaiwenX on this. Attached the mail thread for reference. Could you please let me know if this patch would fix the issue or any more additional fixes are needed? Regards, Amiya On Tue, Feb 6, 2024 at 4:04=E2=80=AFPM David Marchand wrote: > This was reported by RH QE. > > When a vlan is enforced on a VF via an administrative configuration on > the PF side, the net/iavf driver logs two error messages. > Those error messages have no consequence on the rest of the port > initialisation and packet processing works fine. > > [root@toto ~] # ip l set enp94s0 vf 0 vlan 2 > [root@toto ~] # dpdk-testpmd -a 0000:5e:02.0 -- -i > ... > Configuring Port 0 (socket 0) > iavf_dev_init_vlan(): Failed to update vlan offload > iavf_dev_configure(): configure VLAN failed: -95 > iavf_set_rx_function(): request RXDID[1] in Queue[0] is legacy, set > rx_pkt_burst as legacy for all queues > > The first change is to remove the error log in iavf_dev_init_vlan(). > This log is unneeded since all error path are covered by a dedicated log > message already. > > Then, in iavf_dev_init_vlan(), requesting all possible VLAN offloading > must not trigger an ERROR level log message. This is simply confusing, > as the application may not have requested such vlan offloading. > The reason why the driver requests all offloading is unclear so keep it > as is. Instead, rephrase the log message and lower its level to INFO. > > Fixes: 1c301e8c3cff ("net/iavf: support new VLAN capabilities") > Cc: stable@dpdk.org > > Signed-off-by: David Marchand > Acked-by: Bruce Richardson > --- > Changes since v1: > - updated log message, > > --- > drivers/net/iavf/iavf_ethdev.c | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/drivers/net/iavf/iavf_ethdev.c > b/drivers/net/iavf/iavf_ethdev.c > index 1fb876e827..3532e379a1 100644 > --- a/drivers/net/iavf/iavf_ethdev.c > +++ b/drivers/net/iavf/iavf_ethdev.c > @@ -631,7 +631,8 @@ iavf_dev_init_vlan(struct rte_eth_dev *dev) > RTE_ETH_VLAN_FILTER_MASK | > RTE_ETH_VLAN_EXTEND_MASK); > if (err) { > - PMD_DRV_LOG(ERR, "Failed to update vlan offload"); > + PMD_DRV_LOG(INFO, > + "VLAN offloading is not supported, or offloading > was refused by the PF"); > return err; > } > > @@ -707,9 +708,7 @@ iavf_dev_configure(struct rte_eth_dev *dev) > vf->max_rss_qregion =3D IAVF_MAX_NUM_QUEUES_DFLT; > } > > - ret =3D iavf_dev_init_vlan(dev); > - if (ret) > - PMD_DRV_LOG(ERR, "configure VLAN failed: %d", ret); > + iavf_dev_init_vlan(dev); > > if (vf->vf_res->vf_cap_flags & VIRTCHNL_VF_OFFLOAD_RSS_PF) { > if (iavf_init_rss(ad) !=3D 0) { > -- > 2.43.0 > > --=20 This electronic communication and the information and any files transmitted= =20 with it, or attached to it, are confidential and are intended solely for=20 the use of the individual or entity to whom it is addressed and may contain= =20 information that is confidential, legally privileged, protected by privacy= =20 laws, or otherwise restricted from disclosure to anyone else. If you are=20 not the intended recipient or the person responsible for delivering the=20 e-mail to the intended recipient, you are hereby notified that any use,=20 copying, distributing, dissemination, forwarding, printing, or copying of= =20 this e-mail is strictly prohibited. If you received this e-mail in error,= =20 please return the e-mail to the sender, delete it from your computer, and= =20 destroy any printed copy of it. --0000000000008f36790610b5ee95 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi David,

Thanks for the patch.

I also see a si= milar error with iavf using dpdk-22.11.1.=C2=A0But in my case, I see=C2=A0 2 more additional error logs showing up during iavf_de= v_configure(). It's with=C2=A0ESX-8.0U1 with an inbox driver. Firmware = upgrade did not resolve=C2=A0the issue though.

2023-12-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_= log_write:107 iavf_execute_vf_cmd(): Return failure -4 for cmd 27
2023-1= 2-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_log_write:107 i= avf_enable_vlan_strip(): Failed to execute command of OP_ENABLE_VLAN_STRIPP= ING
2023-12-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] = dpdk_log_write:107 iavf_dev_init_vlan(): Failed to update vlan offload
= 2023-12-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_log_write= :107 iavf_dev_configure(): configure VLAN failed: -5
2023-12-08T09:58:0= 1.156 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_log_write:107 iavf_execute_= vf_cmd(): Return failure -5 for cmd 14

I was currently following u= p with KaiwenX on this. Attached the mail thread for reference.=C2=A0
=

<= /div>
= Could you please let me know if this patch would fix the issue or any more = additional fixes are=C2=A0needed?

Regards,
Amiya


On Tue, Feb 6, 2024 at 4:04=E2=80=AFPM David Marchand <<= a href=3D"mailto:david.marchand@redhat.com" target=3D"_blank">david.marchan= d@redhat.com> wrote:
This was reported by RH QE.

When a vlan is enforced on a VF via an administrative configuration on
the PF side, the net/iavf driver logs two error messages.
Those error messages have no consequence on the rest of the port
initialisation and packet processing works fine.

[root@toto ~] # ip l set enp94s0 vf 0 vlan 2
[root@toto ~] # dpdk-testpmd -a 0000:5e:02.0 -- -i
...
Configuring Port 0 (socket 0)
iavf_dev_init_vlan(): Failed to update vlan offload
iavf_dev_configure(): configure VLAN failed: -95
iavf_set_rx_function(): request RXDID[1] in Queue[0] is legacy, set
=C2=A0 =C2=A0 =C2=A0 =C2=A0 rx_pkt_burst as legacy for all queues

The first change is to remove the error log in iavf_dev_init_vlan().
This log is unneeded since all error path are covered by a dedicated log message already.

Then, in iavf_dev_init_vlan(), requesting all possible VLAN offloading
must not trigger an ERROR level log message. This is simply confusing,
as the application may not have requested such vlan offloading.
The reason why the driver requests all offloading is unclear so keep it
as is. Instead, rephrase the log message and lower its level to INFO.

Fixes: 1c301e8c3cff ("net/iavf: support new VLAN capabilities") Cc: stable@dpdk.org

Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
---
Changes since v1:
- updated log message,

---
=C2=A0drivers/net/iavf/iavf_ethdev.c | 7 +++----
=C2=A01 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/drivers/net/iavf/iavf_ethdev.c b/drivers/net/iavf/iavf_ethdev.= c
index 1fb876e827..3532e379a1 100644
--- a/drivers/net/iavf/iavf_ethdev.c
+++ b/drivers/net/iavf/iavf_ethdev.c
@@ -631,7 +631,8 @@ iavf_dev_init_vlan(struct rte_eth_dev *dev)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 RTE_ETH_= VLAN_FILTER_MASK |
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 RTE_ETH_= VLAN_EXTEND_MASK);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (err) {
-=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PMD_DRV_LOG(ERR, &q= uot;Failed to update vlan offload");
+=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PMD_DRV_LOG(INFO, +=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0"VLAN offloading is not supported, or offloading was refused= by the PF");
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 return err;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }

@@ -707,9 +708,7 @@ iavf_dev_configure(struct rte_eth_dev *dev)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 vf->max_rss_qreg= ion =3D IAVF_MAX_NUM_QUEUES_DFLT;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }

-=C2=A0 =C2=A0 =C2=A0 =C2=A0ret =3D iavf_dev_init_vlan(dev);
-=C2=A0 =C2=A0 =C2=A0 =C2=A0if (ret)
-=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PMD_DRV_LOG(ERR, &q= uot;configure VLAN failed: %d", ret);
+=C2=A0 =C2=A0 =C2=A0 =C2=A0iavf_dev_init_vlan(dev);

=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (vf->vf_res->vf_cap_flags & VIRTCH= NL_VF_OFFLOAD_RSS_PF) {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (iavf_init_rss(a= d) !=3D 0) {
--
2.43.0


This ele= ctronic communication and the information and any files transmitted with it= , or attached to it, are confidential and are intended solely for the use o= f the individual or entity to whom it is addressed and may contain informat= ion that is confidential, legally privileged, protected by privacy laws, or= otherwise restricted from disclosure to anyone else. If you are not the in= tended recipient or the person responsible for delivering the e-mail to the= intended recipient, you are hereby notified that any use, copying, distrib= uting, dissemination, forwarding, printing, or copying of this e-mail is st= rictly 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. --0000000000008f36790610b5ee95-- --0000000000008f367b0610b5ee97 Content-Type: message/rfc822; name="Regarding https___mails.dpdk.org_archives_dev_2023-June_270558.html dpdk patch.eml" Content-Disposition: attachment; filename="Regarding https___mails.dpdk.org_archives_dev_2023-June_270558.html dpdk patch.eml" Content-ID: X-Attachment-Id: f_lsacf62o0 MIME-Version: 1.0 Date: Mon, 5 Feb 2024 16:38:27 +0530 References: In-Reply-To: Message-ID: Subject: Re: Regarding https://mails.dpdk.org/archives/dev/2023-June/270558.html dpdk patch From: Amiya Ranjan Mohakud To: "Deng, KaiwenX" Cc: "dev@dpdk.org" , Amiya Ranjan Mohakud Content-Type: multipart/alternative; boundary="00000000000035d2d10610a07b5f" --00000000000035d2d10610a07b5f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=3D= io&productid=3D37976 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=E2=80=AFAM Deng, KaiwenX wrote: > Hi Amiya > > > > Can you provide me with the DPDK startup parameters? > > > > Thanks > > *From:* Amiya Ranjan Mohakud > *Sent:* Tuesday, January 23, 2024 4:54 PM > *To:* Deng, KaiwenX ; dev@dpdk.org > *Cc:* Amiya Ranjan Mohakud ; Amiya > Ranjan Mohakud > *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 bel= ow > 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=3D1, rxq/txq=3D1/1, (rss_enabled=3D1) > rss_hf=3D0x0000000000000c30 tx_ol=3D0x00000000000006 rx_ol=3D0x0000000008= 0007 > > 2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_exe= cute_vf_cmd(): Return failure -4 for cmd 27 > > 2023-12-08T09:58:00.906 |9322| MSG [NET] dpdk_log_write:107 iavf_ena= ble_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_exe= cute_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 an= d > may contain information that is confidential, legally privileged, protect= ed > by privacy laws, or otherwise restricted from disclosure to anyone else. = If > you are not the intended recipient or the person responsible for deliveri= ng > the e-mail to the intended recipient, you are hereby notified that any us= e, > 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. > --00000000000035d2d10610a07b5f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Kaiwenx<= /span>,=C2=A0

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

=
Just for an additional update = -=C2=A0=C2=A0

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

I tried = updating the firmware version to=C2=A09.00 0x8000cadc 21.5.9 based on the c= ompatibility matrix=C2=A0https://www.v= mware.com/resources/compatibility/detail.php?deviceCategory=3Dio&produc= tid=3D37976
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= =C2=A0any breakthroughs. Thanks in advance.


=
Regards,
Amiya


On = Thu, Jan 25, 2024 at 11:40=E2=80=AFAM Deng, KaiwenX <kaiwenx.deng@intel.com> wro= te:

Hi Amiya

=C2=A0

Can you provide me with the DPDK startup parameters?=

=C2=A0

Thanks

From: Amiya Ranjan Mohakud <amiya-ranjan.mohak= ud@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

=C2=A0

Hi Ka= iwenx

=C2=A0

I cam= e across the below DPDK iavf error message during the initialization of X71= 0 NICs in ESX.=C2=A0 It seems the functionality works fine, but with below = error messages.

DPDK = Version: 22.11.2

=C2=A0

2023-12-08T09:58:00.= 901 |9322| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_port_configure:1717 Configure= port eth3/1. lsc_intr=3D1, rxq/txq=3D1/1, (rss_enabled=3D1) rss_hf=3D0x000= 0000000000c30 tx_ol=3D0x00000000000006 rx_ol=3D0x00000000080007

2023-12-08T09:58:00.906 |93=
22| MSG =C2=A0 =C2=A0 =C2=A0[NET] dpdk_log_write:107 iavf_execute_vf_cmd():=
 Return failure -4 for=
 cmd 27
2023-12-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[N=
ET] 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 =C2=A0 =C2=A0 =C2=A0[N=
ET] dpdk_log_write:107 iavf_dev_init_vlan(): Failed to update vlan offload =

2023-12-08T09:58:00.906 |9322| MSG =C2=A0 =C2=A0 =C2=A0[N=
ET] dpdk_log_write:107 iavf_dev_configure(): configure VLAN failed: -5 <=
/u>
2023-12-08T09:58:01.156 |9322| MSG =C2=A0 =C2=A0 =C2=A0[N=
ET] dpdk_log_write:107 iavf_execute_vf_cmd(): Return failure -5 for cmd 14



=C2=A0






On se=
arch, I came across your above patch. I am not able to make out properly fr=
om the=C2=A0description. 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.=C2=A0






=C2=A0










Regar=
ds,




Amiya=


This electronic= communication and the information and any files transmitted with it, or at= tached to it, are confidential and are intended solely for the use of the i= ndividual or entity to whom it is addressed and may contain information that is confidential, legally privil= eged, protected by privacy laws, or otherwise restricted from disclosure to= anyone else. If you are not the intended recipient or the person responsib= le for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, dis= tributing, dissemination, forwarding, printing, or copying of this e-mail i= s 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.

--00000000000035d2d10610a07b5f-- --0000000000008f367b0610b5ee97--