From: Alireza Sanaee <sarsanaee@gmail.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Problem in configuring rxmode.mq_mode
Date: Fri, 17 Jul 2020 02:55:59 +0800 [thread overview]
Message-ID: <3a9f946f-7384-2219-bd46-c3d1485a49ba@gmail.com> (raw)
In-Reply-To: <AM0PR05MB6707C1B4EFA5540F6C673F3BC27F0@AM0PR05MB6707.eurprd05.prod.outlook.com>
Hello,
Thanks for the message,
It actually helped, and it now complies with RSS configuration using the
patch. I also suspect that there is some sort of similar problem
concerned with adding more flow rules as well. I added different rules
to steer flows on a specific queue, however, DPDK seems to be totally
unresponsive to my rules. Is there any idea here?
I'm using DPDK 19.11.1!
Thanks,
Alireza
On 7/16/20 11:32 PM, Raslan Darawsheh wrote:
> Hi Alireza,
>
> We had this issue in old releases, and it has been fixed by this patch:
> http://patches.dpdk.org/patch/69554/
> can you check if it will solve your issue?
>
> Kindest regards,
> Raslan Darawsheh
>
>> -----Original Message-----
>> From: users <users-bounces@dpdk.org> On Behalf Of Alireza Sanaee
>> Sent: Thursday, July 16, 2020 3:11 PM
>> To: users@dpdk.org
>> Subject: [dpdk-users] Problem in configuring rxmode.mq_mode
>>
>> Dear all,
>>
>> I'd like to configure my NIC to not use RSS, however, it seems NIC
>> doesn't adhere to the configurations set in the code, and it just
>> applies a default RSS config. Particularly, I turned the RSS config off
>> using `.mq_mode = ETH_MQ_RX_NONE`, but my NIC still keeps landing
>> different flows on different queues. I have got a Mellanox ConnectX-4 NIC.
>>
>> Thanks,
>> Alireza
next prev parent reply other threads:[~2020-07-16 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 12:11 Alireza Sanaee
2020-07-16 15:32 ` Raslan Darawsheh
2020-07-16 18:55 ` Alireza Sanaee [this message]
2020-07-17 14:01 ` Alireza Sanaee
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=3a9f946f-7384-2219-bd46-c3d1485a49ba@gmail.com \
--to=sarsanaee@gmail.com \
--cc=rasland@mellanox.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).