From: "Pathak, Pravin" <pravin.pathak@intel.com>
To: Adel Belkhiri <adel.belkhiri@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: Problem configuring vhost-user NICs with multi queues (RSS) support
Date: Wed, 8 Jun 2022 00:30:53 +0000 [thread overview]
Message-ID: <BL1PR11MB54616665C4F97F5DD0D158CAF4A49@BL1PR11MB5461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMxxxdN++CFz9YEPKmcYq_AbsnAyyqLRfwE+1AwnzYjEqcqF7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
Does your traffic have multiple 5 tuple flows to distribute it across multiple Rx queues?
From: Adel Belkhiri <adel.belkhiri@gmail.com>
Sent: Tuesday, June 7, 2022 7:29 PM
To: users@dpdk.org
Subject: Problem configuring vhost-user NICs with multi queues (RSS) support
Hi all,
I have a problem with the configuration of the sample application l3fdw for switching traffic between two vhost-user NICs, each with 4 queues. The traffic was generated using TREX, running inside a VM.
When I traced my experiment, I noticed that the traffic was only received in queue "0", while the other RX queues were empty. When I run the application, a msg is printed "Port 1 modified RSS hash function based on hardware support,requested:0xa38c configured:0".
It seems that while the vhost-user NIC implementation supports multiple queues, it does not support distributing the traffic between the RX queues.
I wonder if there is a way to make it work?
Thank you,
PS:
- DPDK version: 19.08
- Qemu version: 4.2.1
Adele
[-- Attachment #2: Type: text/html, Size: 4266 bytes --]
next prev parent reply other threads:[~2022-06-08 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 23:28 Adel Belkhiri
2022-06-08 0:30 ` Pathak, Pravin [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-07 23:25 Adel Belkhiri
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=BL1PR11MB54616665C4F97F5DD0D158CAF4A49@BL1PR11MB5461.namprd11.prod.outlook.com \
--to=pravin.pathak@intel.com \
--cc=adel.belkhiri@gmail.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).