From: Yang Luan <luan.penny@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Wrong rx queue assignment running DPDK on Azure
Date: Fri, 4 Nov 2022 10:15:36 -0700 [thread overview]
Message-ID: <CAPHT=bY0bs8KYha6tMf7n375kRnjQ0OSbv938OLvYLFPRAqpYQ@mail.gmail.com> (raw)
In-Reply-To: <20221104095202.32c55020@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]
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).
On Fri, Nov 4, 2022 at 9:52 AM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Tue, 1 Nov 2022 17:25:24 -0700
> Yang Luan <luan.penny@gmail.com> wrote:
>
> > Hello,
> >
> >
> > Our application uses the net_netvsc driver in DPDK 21.08 on Azure. We
> found
> > an issue where RSS doesn’t deliver packets to the correct rx queue. The
> > instance type we use is Standard_L80s_v3 with MT27800 Family [ConnectX-5
> > Virtual Function] NICs. The NIC is configured with 40 rx queues and the
> > RETA table is configured (confirmed by rte_eth_dev_rss_reta_query()) as
> > below.
> >
> >
> >
> > 0: 0 1 2 3 4 5 6 7
> >
> > 8: 8 9 10 11 12 13 14 15
> >
> > 16: 16 17 18 19 20 21 22 23
> >
> > 24: 24 25 26 27 28 29 30 31
> >
> > 32: 32 33 34 35 36 37 38 39
> >
> > 40: 0 1 2 3 4 5 6 7
> >
> > 48: 8 9 10 11 12 13 14 15
> >
> > 56: 16 17 18 19 20 21 22 23
> >
> > 64: 24 25 26 27 28 29 30 31
> >
> > 72: 32 33 34 35 36 37 38 39
> >
> > 80: 0 1 2 3 4 5 6 7
> >
> > 88: 8 9 10 11 12 13 14 15
> >
> > 96: 16 17 18 19 20 21 22 23
> >
> > 104: 24 25 26 27 28 29 30 31
> >
> > 112: 32 33 34 35 36 37 38 39
> >
> > 120: 0 1 2 3 4 5 6 7
> >
> >
> >
> > One example is a packet received with rss key 0xEDE25D84 was incorrectly
> > delivered to rx queue 12. We expect it to be queue 4 as 0xEDE25D84 &
> 0x7F =
> > 4 assuming seven of the least significant bits (LSBs) are used for
> indexing
> > into the RETA table. Is it a bug or we made a wrong assumption on how
> the
> > RETA table is accessed with that device?
> >
> >
> > Thank you.
> >
> > Yang
>
> Are you using failsafe PMD or the native netvsc PMD?
> Are you programming reta table via DPDK or through other API's?
>
[-- Attachment #2: Type: text/html, Size: 3288 bytes --]
next prev parent reply other threads:[~2022-11-07 9:12 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 [this message]
2022-11-04 22:18 ` Stephen Hemminger
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='CAPHT=bY0bs8KYha6tMf7n375kRnjQ0OSbv938OLvYLFPRAqpYQ@mail.gmail.com' \
--to=luan.penny@gmail.com \
--cc=stephen@networkplumber.org \
--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).