From: Stephen Hemminger <stephen@networkplumber.org>
To: Yang Luan <luan.penny@gmail.com>
Cc: users@dpdk.org
Subject: Re: Wrong rx queue assignment running DPDK on Azure
Date: Fri, 4 Nov 2022 15:18:03 -0700 [thread overview]
Message-ID: <20221104151803.5eb40caa@hermes.local> (raw)
In-Reply-To: <CAPHT=bY0bs8KYha6tMf7n375kRnjQ0OSbv938OLvYLFPRAqpYQ@mail.gmail.com>
On Fri, 4 Nov 2022 10:15:36 -0700
Yang Luan <luan.penny@gmail.com> wrote:
> We use netvsc PMD (drivers/net/netvsc/).
> We don't explicitly configure the RETA table. We configure the device with
> 40 rx queues (rte_eth_dev_configure) and use rte_eth_dev_rss_reta_query()
> to query the RETA table (result posted earlier).
More questions to help someone (not me I don't have free Azure access now);
get a reproduction.
Did you reconfigure the RSS key?
The default for the netvsc PMD should be the same default as Mellanox.
Have you enabled accelerated networking (ie VF). If so then does your DPDK
build support Mellanox. Probably yes to both.
Is this the first packet, or later packets in the flow?
Are you using any layered encapsulation (like GRE or VXLAN), and/or IP options.
Are you changing RSS options so that is different than default L3/L4?
Are you printing the RSS key in the mbuf? It might be byte swapped.
Why 21.08? it is not a long term supported version, and therefore does not
receive bugfixes like:
$ git log --oneline v21.08..v20.11.6 -- drivers/net/netvsc/
9d474a9565a5 net/netvsc: fix vmbus device reference in multi-process
a61bd9df25dc net/netvsc: fix calculation of checksums based on mbuf flag
0b5a6c7b32c8 fix spelling in comments and strings
e97bb2a91151 net/netvsc: ignore unsupported packet on sync command
next prev parent reply other threads:[~2022-11-04 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 0:25 Yang Luan
2022-11-04 16:52 ` Stephen Hemminger
2022-11-04 17:15 ` Yang Luan
2022-11-04 22:18 ` Stephen Hemminger [this message]
2022-11-07 20:03 ` Yang Luan
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=20221104151803.5eb40caa@hermes.local \
--to=stephen@networkplumber.org \
--cc=luan.penny@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).