From: Tony Hart <tony.hart@domainhart.com>
To: users@dpdk.org
Subject: mlx5: imissed versus prio0_buf_discards
Date: Sat, 12 Oct 2024 11:08:30 -0400 [thread overview]
Message-ID: <CAC6tBwxQde5bAVwddN6HU9yt=_aPzjGwodEoiPrFzxFKHQ68CA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
I have a simple DPDK app that receives packets via RSS from a CX7 (400G).
The app uses 16 queues across 16 cores. What I see is dropped packets even
at only 50Mpps.
Looking at rte_eth_port_xstats() I see rx_prio0_buf_discard_packets
matches the number of packets dropped however the imissed counter (from
rte_eth_port_stats) is 0. Indeed when I look at the rx_queue depths from
each thread in the app they barely reach 30 entries (I'm using the default
number of queue descs).
What is the difference between rx_prio0_buf_discards and imissed counters,
why would rx_prio0_buf_discards increase but not imissed?
many thanks,
tony
fyi: this is using DPKD 24.07 and the HWS RTE FLOW Api to setup the RSS
flow. Firmware is 28.41
[-- Attachment #2: Type: text/html, Size: 1111 bytes --]
reply other threads:[~2024-10-12 15:08 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='CAC6tBwxQde5bAVwddN6HU9yt=_aPzjGwodEoiPrFzxFKHQ68CA@mail.gmail.com' \
--to=tony.hart@domainhart.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).