DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajay Thakur <ajaykt665@gmail.com>
To: dev@dpdk.org
Subject: need support with struct rte_eth_fdir_conf fdir_conf
Date: Sun, 12 Mar 2023 16:10:08 +0530	[thread overview]
Message-ID: <CACidQMAWnJpy8XWrwfYSNtaM2ykzygo9OhuXvkCdtB-tWRofTA@mail.gmail.com> (raw)

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

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 *

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

                 reply	other threads:[~2023-03-12 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CACidQMAWnJpy8XWrwfYSNtaM2ykzygo9OhuXvkCdtB-tWRofTA@mail.gmail.com \
    --to=ajaykt665@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).