DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Joshi, Venkatesh" <venkatesh.joshi@hpe.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Flexible payload feature of i40e PMD in DPDK 20.11
Date: Tue, 31 Jan 2023 13:40:01 -0800	[thread overview]
Message-ID: <20230131134001.522b20c3@hermes.local> (raw)
In-Reply-To: <MN0PR84MB3047C7F7EF940AAD3775E3D6ECD09@MN0PR84MB3047.NAMPRD84.PROD.OUTLOOK.COM>

On Tue, 31 Jan 2023 18:44:51 +0000
"Joshi, Venkatesh" <venkatesh.joshi@hpe.com> wrote:

> Hi,
> 
> I have the following configuration:
> 
> NIC: Intel XXV710 (supported by i40e PMD)
> DPDK version: 20.11
> 
> My requirement is to use Flexible payload of the XXV710 NIC (i40e PMD) to do the following:
> 
> * For incoming packets where the ethertype is 0x0806 (ie: ARP packets), do the RSS hashing based on the Sender Hardware Address instead of the ethertype field which is considered by default. 
> * Basically, I don't want all the ARP packets falling on the same queue. Hence, hashing based on the sender hardware address would give a good distribution across multiple CPUs where my dpdk application is running.
> 
> 
> However, I have not been able to find any examples where the following macros have been used - RTE_ETH_INPUT_SET_FLEX_PAYLOAD_1ST_WORD through RTE_ETH_INPUT_SET_FLEX_PAYLOAD_8TH_WORD.
> 
> 
> Any pointers would be much appreciated.

The old flow direct stuff is deprecated.

What you want could be done via rte_flow API by defining a match for ARP (ethertype)
and action of rte_eth_flow_action_rss of type L2_PAYLOAD and pointing at the sender.

But that assumes the i40e driver implements all this and it doesn't.

You probably have to live will ARP arriving on single queue and do any fanout you want
using rte_ring's.


      reply	other threads:[~2023-01-31 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 18:44 Joshi, Venkatesh
2023-01-31 21:40 ` Stephen Hemminger [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=20230131134001.522b20c3@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=venkatesh.joshi@hpe.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).