From: spyroot <spyroot@gmail.com>
To: users@dpdk.org
Subject: IAVF/ICEN Intel 810 (i.e SRIOV case) 16 queue and RSS dpdk-tested report single queue pps / stats
Date: Fri, 18 Apr 2025 22:30:43 +0400 [thread overview]
Message-ID: <CABsV3rA5d=Hu3N5y3kCehV0+EpadqmLEEpcWyCdJO-0MhQZQRw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Folks,
I am observing that DPDK test-pmd with IAVF PMD, ICEN PF driver,
reporting statistics incorrectly when the RX side generates a UDP flow
that randomizes or increments IP/UDP header data (IP/port, etc).
I tested all 23.x stable and all branches.
-If I use *single* flow (on the TX side, all tuples are the same on the RX
HASH() produce -> same result). no issue.
So, on the RX side, I see all zero packet drops and the correct pps
value reported by test-pmd.
- If I increase the number of flows ( IP/UDP, etc.), the PPS Counter
and byte/pkt counter
report only single queues. (i.e, it looks to me like it uses some
default queue 0
or something and skips the rest 15 (in my case --rxq=16). (It could
IAVF do that or ICEN report that). I'm not sure.
For example, the counter I'm referring to test-pmd Rx-pps counter.
Rx-pps: 4158531 Rx-bps: 2129167832
I'm also observing PMD Failing fetch stats error msg.
iavf_query_stats(): fail to execute command OP_GET_STATS
iavf_dev_stats_get(): Get statistics failed
My Question.
If I have two instances of
test-pmd --allowed X
test-pmd --allowed Y
Where X is VFs PCI ADDR X and Y PCI ADDR Y from the PF?
I expect to see the total stats (pps/bytes, etc.) (combined value for
all 16 queues for a port 0 )
RX-PPS and bytes per port on both instances.
Yes/No?
Has anyone had a similar issue in the past?
Thank you,
MB
[-- Attachment #2: Type: text/html, Size: 7763 bytes --]
reply other threads:[~2025-04-18 18:30 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='CABsV3rA5d=Hu3N5y3kCehV0+EpadqmLEEpcWyCdJO-0MhQZQRw@mail.gmail.com' \
--to=spyroot@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).