From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1836] bnxt underreporting stats when queue count > RTE_ETHDEV_QUEUE_STAT_CNTRS
Date: Wed, 26 Nov 2025 17:05:36 +0000 [thread overview]
Message-ID: <bug-1836-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1836
Bug ID: 1836
Summary: bnxt underreporting stats when queue count >
RTE_ETHDEV_QUEUE_STAT_CNTRS
Product: DPDK
Version: 24.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: oleksandrn@interfacemasters.com
Target Milestone: ---
Basically, if you have more than RTE_ETHDEV_QUEUE_STAT_CNTRS queues, it will
underreport counters, specifically, ipacket, ibytes, and so on, so like total
port stats, not per queue ones.
I did a little bit of investigation:
bnxt_stats_get_op/bnxt_stats_get_ext both have this line
num_q_stats = RTE_MIN(bp->rx_cp_nr_rings,
(unsigned int)RTE_ETHDEV_QUEUE_STAT_CNTRS);
Then, in the loop, bnxt_hwrm_ring_stats is called to retrieve stats for the
queue, and bnxt_fill_rte_eth_stats is used to aggregate results and actually
add values to ipacket/ibytes; however, if rx_cp_nr_rings >
RTE_ETHDEV_QUEUE_STAT_CNTRS, it means that some queues are never checked.
Maybe there are hardware limitations I'm not aware of, but it seems like a bug
to me.
Originally saw this on 24.07, and now we are moving to 25, but just from the
code, it seems like 25 will have the same problem, but I haven't tried with
traffic yet on 25.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-11-26 17:05 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=bug-1836-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).