From: "Joshi, Venkatesh" <venkatesh.joshi@hpe.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Is it possible to configure different default queues per port
Date: Fri, 21 May 2021 04:51:51 +0000 [thread overview]
Message-ID: <TU4PR8401MB047913D13ADD6F42A1ACC352EC299@TU4PR8401MB0479.NAMPRD84.PROD.OUTLOOK.COM> (raw)
Hi,
We are using DPDK 20.08 and Intel XXV710 NIC (firmware version 7.3)
We have a dpdk application running as 4 processes on 4 CPUs.
And, we have 4 ports for the ingress traffic.
* Each port has been configured with 4 Rx Queues (from 0 to 3) and each Rx Queue is bound to a unique CPU.
With RSS hashing mechanism, the incoming packets will get hashed and fall into one of the 4 queues.
But, when RSS hashing fails or cannot be done, the incoming packets are enqueued into Queue 0 on each port because this is the default queue.
Is it possible to change the default queue so that, for each port, there is a different default queue. Eg:
- For port 0, the default queue is 0 ,
- For port 1, the default queue is 1 and so on.
Regards,
Venkatesh
reply other threads:[~2021-05-21 4:52 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=TU4PR8401MB047913D13ADD6F42A1ACC352EC299@TU4PR8401MB0479.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).