DPDK usage discussions
 help / color / mirror / Atom feed
From: "Joshi, Venkatesh" <venkatesh.joshi@hpe.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Enabling Flow Director functionality on XL710 NICs with rte_flow API
Date: Wed, 2 Dec 2020 18:56:04 +0000	[thread overview]
Message-ID: <AT5PR8401MB10270163CED54D0479FC5587ECF30@AT5PR8401MB1027.NAMPRD84.PROD.OUTLOOK.COM> (raw)

Hi,

We have a DPDK application that will make use of the "Intel flow director" feature of the XXV710 NIC family.

DPDK Version - 20.08
NIC: XXV710 series


I am planning to use the rte_flow API for this. I have gone through the flow_filtering example application for this purpose.

Previously, I saw on this forum that the following code snippet was in use for enabling the flow director feature - 
----
struct rte_eth_conf port_conf = {
    ... 
    ... 
    .fdir_conf = {
        .mode = RTE_FDIR_MODE_PERFECT,
        .pballoc = RTE_FDIR_PBALLOC_128K,
        .status = RTE_FDIR_REPORT_STATUS,
        .drop_queue = 127,
        .mask = {
            .ipv4_mask     = {
                .src_ip = 0xFFFFFFFF,
                .dst_ip = 0xFFFFFFFF,
            },
            .ipv6_mask     = {
                .src_ip = {0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF},
                .dst_ip = {0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF},
            },
            .src_port_mask = 0xFFFF,
            .dst_port_mask = 0xFFFF,
        },
    },
    ... 
    ... 
}
---

Questions:
* Is this initialization of the fdir_conf not required when we use the rte_flow API ?
* What do we need to do to initialize flow director feature with rte_flow API?


PS: It seems that the fdir_conf is going to get obsolete in the future DPDK releases.

Regards,
Venkatesh



                 reply	other threads:[~2020-12-02 18:56 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=AT5PR8401MB10270163CED54D0479FC5587ECF30@AT5PR8401MB1027.NAMPRD84.PROD.OUTLOOK.COM \
    --to=venkatesh.joshi@hpe.com \
    --cc=users@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).