From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1275] About i40e statistics: When all packets overruns, rx_packets is 0, but rx_bytes still increasing
Date: Thu, 17 Aug 2023 07:11:43 +0000 [thread overview]
Message-ID: <bug-1275-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1275
Bug ID: 1275
Summary: About i40e statistics: When all packets overruns,
rx_packets is 0, but rx_bytes still increasing
Product: DPDK
Version: 20.08
Hardware: ARM
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: zwt250058@163.com
Target Milestone: ---
Driver: i40e, 8086:1572
I run dpdk program with i40e nic. When all packet overruns, the “rx_packets”
stop increasing, and I found “rx_bytes” is still increasing, which i think, is
expected to stop increasing. The statistics comes from the function
"rte_eth_stats_get()"
Could you please help me to find the reason?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2853 bytes --]
next reply other threads:[~2023-08-17 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 7:11 bugzilla [this message]
2024-04-02 2:33 ` [DPDK/ethdev Bug " bugzilla
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-1275-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).