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: [dpdk-users] Ref: Excluding certain Rx Queues from the RSS hashing algorithm
Date: Mon, 5 Apr 2021 08:11:17 -0700
Message-ID: <20210405081117.7ec69e25@hermes.local> (raw)
In-Reply-To: <TU4PR8401MB0479318157552E5CEABF9DE2EC779@TU4PR8401MB0479.NAMPRD84.PROD.OUTLOOK.COM>

On Mon, 5 Apr 2021 03:10:21 +0000
"Joshi, Venkatesh" <venkatesh.joshi@hpe.com> wrote:

> Hi,
> We use the following hardware/software in our product:
> * CPU: Intel Xeon Silver 4210
> * NIC: XXV710-AM2
> * NIC Firmware: 7.3/8.0
> * Linux Kernel version: 4.14
> * DPDK version: 20.08
> * vfio-pci driver
> Our DPDK application runs on 7 CPU threads. We have initialized 7 Rx Queues - one for each CPU thread.
> We want to use one of the queues exclusively for traffic that matches Flow Director rules.
> And, we want that when the RSS hashing algorithm provides action as Enqueue - it should not use that queue during its computation.
> Example: We initialize Rx Queues 0 to 6.
> Out of this, we want that Rx Queue 0 to 5 be used in the RSS hash algorithm when the action is enqueue.
> Rx Queue 6 should be kept out of the RSS hashing logic.
> This is wrt the i40e driver.
> Is this possible?
> regards,
> venkatesh

The hashing logic relative to flow rules is confused in DPDK.
Have you tried programming two rules, one for the traffic you want, and the other at lower priority which
is a match any rule?

Also, fdir is deprecated in DPDK, please consider using rte_flow instead.

      reply	other threads:[~2021-04-05 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05  3:10 Joshi, Venkatesh
2021-04-05 15:11 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210405081117.7ec69e25@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=venkatesh.joshi@hpe.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git