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 A2B1A41E20; Sun, 12 Mar 2023 16:28:18 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 91E1840F18; Sun, 12 Mar 2023 16:28:18 +0100 (CET) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) by mails.dpdk.org (Postfix) with ESMTP id 2E553406A2 for ; Sun, 12 Mar 2023 11:40:22 +0100 (CET) Received: by mail-lj1-f182.google.com with SMTP id b10so9835573ljr.0 for ; Sun, 12 Mar 2023 03:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678617621; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=2Cxfp0UX2gtDUbS7uvfOTLl9U9XMGGNLHHOkUCSiDmw=; b=n7fNU6fy3VNb3+pdwMynm+PkBGK9VJClzppjy70IYwCp6TyXEcbf9kn0TDOyHpdQY/ soZ0pB+K26Y0gQsEzL/zyjvBTc6uPH3OaqWK18c081DVVQ0uZAk1eozHe8kfrxjU+50K dXB6u9PlOhAKejQhB2Q4CQnOFGTpx+ASp7nSU1PHf97DWwhj8W9MwgaElHkjHeVrZM/5 MwRWIRjxr5cpFtk1aIq22rn0l+rrn2WkbLeDOs5HnyC0R+6D2ZXHr0f+FBEomF0tw101 1VQFkJxNUEVX0yLaxvwRq1Asvbteuc5cppumkQZ2umW7b5t5+Et0OJhA/IXHe28xOJzu 6IOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678617621; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=2Cxfp0UX2gtDUbS7uvfOTLl9U9XMGGNLHHOkUCSiDmw=; b=Ee3/4DW6EwTKpkNsXRxxGjO2UbeEfZ1A+MhozzOf3bBTZV8EnLN2lq22sTgGqRPICx q3PuPGg6m0oAy2qKmtGMo0lyjgJX+n53Cgg0e3QH0jx/QzK1lDuOAQr4HdN95infN4Qs QCt5UIpXueazzuTQDx/eJ2ww9JUhOtU9mM724J7MhVyyjDWJ2s5ZigdGbrTK+aNil/9K 6rxGQcbQx3LUhCiP1rbPfA4UgKA53kWVa2Z67dyWEg8Sv6Hv+0OTDFnIl2hPk1HyZtsP PhJgqdLtyKObbFSRTUjXr4VLbPFr6ofq/68dK3RUybtnJdplknSPwa0PXP/X8p0AJpqQ V5Mw== X-Gm-Message-State: AO0yUKUUMLmKgtBssFrlxusYlBVrG+TxuL7gESgoaXfpSf3xNuz9J/oT +E7gIxwUkrpktvYlDJLS5OMfISvaliqtmBuzYP6pDYrs43s= X-Google-Smtp-Source: AK7set9yc4fwTCWv3ifnZ/XvgtJz3wJhrfpsEKPFiWld162tPiyEyn9s+2xc2XH9two3nieog+y221G9Xgxj1AMUPIw= X-Received: by 2002:a2e:b522:0:b0:298:72a8:c6c4 with SMTP id z2-20020a2eb522000000b0029872a8c6c4mr3780991ljm.9.1678617620556; Sun, 12 Mar 2023 03:40:20 -0700 (PDT) MIME-Version: 1.0 From: Ajay Thakur Date: Sun, 12 Mar 2023 16:10:08 +0530 Message-ID: Subject: need support with struct rte_eth_fdir_conf fdir_conf To: dev@dpdk.org Content-Type: multipart/alternative; boundary="000000000000fcb08805f6b19ec1" X-Mailman-Approved-At: Sun, 12 Mar 2023 16:28:16 +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 --000000000000fcb08805f6b19ec1 Content-Type: text/plain; charset="UTF-8" Hi, I am trying to upgrade vpp20.09 with dpdk 22.11 from vpp20.09 with dpdk 21.11. So it is just DPDK i am trying to upgrade to 22.11. I am encountering an issue with one of the structures. The structure *struct rte_eth_fdir_conf fdir_conf*; /**< FDIR configuration. DEPRECATED */ is deprecated in dpdk 22.11. while dealing with the vpp code: VPP/vpp-20.09/srcPatched/src/plugins/dpdk/device/common.c, there is a piece of code which has dependency to above structure. if (xd->pmd == VNET_DPDK_PMD_I40E) { if ((xd->flags & DPDK_DEVICE_FLAG_RX_FLOW_OFFLOAD) != 0) xd->port_conf.*fdir_conf*.mode = RTE_FDIR_MODE_PERFECT; else xd->port_conf.*fdir_conf*.mode = RTE_FDIR_MODE_NONE; } while checking the vpp source of 23.02, i see above code from common.c (function dpdk_device_setup line 82) being removed. After seeing the dpdk 22.11 release notes, the structure *struct rte_eth_fdir_conf fdir_conf *has moved to ethdev_driver.h which is internal and not supposed to be used by the user. so what is the alternative to this. Do i need to retain the above piece of code in my upgrade activity? -- *Regards,* *Ajay * --000000000000fcb08805f6b19ec1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
I am trying to upgrade vpp20.09 with dpdk 22.11 fr= om vpp20.09 with dpdk 21.11. So it is just DPDK i am trying to upgrade to 2= 2.11.
I am encountering an issue=C2=A0with one of the structures.= The structure=C2=A0struct rte_eth_fdir_conf fdir_conf; /**< FDIR= configuration. DEPRECATED */ is deprecated in dpdk 22.11.=C2=A0
= while dealing with the vpp code:=C2=A0VPP/vpp-20.09/srcPatched/src/plugins/= dpdk/device/common.c, there is a piece of code which has dependency to abov= e structure.

if (xd->pmd =3D=3D VNET_DPDK_PMD_I= 40E)
=C2=A0 =C2=A0 { =C2=A0
=C2=A0 =C2=A0 =C2=A0 if ((xd->flags &= amp; DPDK_DEVICE_FLAG_RX_FLOW_OFFLOAD) !=3D 0)
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 xd->port_conf.fdir_conf.mode =3D RTE_FDIR_MODE_PERFECT;
= =C2=A0 =C2=A0 =C2=A0 else
=C2=A0 =C2=A0 =C2=A0 =C2=A0 xd->port_conf.<= b>fdir_conf.mode =3D RTE_FDIR_MODE_NONE;
=C2=A0 =C2=A0 }

while checking the vpp source of 23.02, i see above code = from common.c (function=C2=A0dpdk_device_se= tup=C2=A0line 82) being removed.
After seeing the dpdk 22.= 11 release notes, the structure=C2=A0struct rte_eth_fdir_conf fdir_conf = has moved to ethdev_driver.h which is internal and=C2=A0 not supposed t= o be used by the user.
so what is the alternative to this.=C2=A0D= o i need to retain the above piece of code in my upgrade activity?




--
=
=
=

Regards,<= /div>
Ajay=C2=A0
<= /div>
--000000000000fcb08805f6b19ec1--