From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 521] i40e: incorrect byte counters
Date: Fri, 07 Aug 2020 15:36:42 +0000 [thread overview]
Message-ID: <bug-521-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=521
Bug ID: 521
Summary: i40e: incorrect byte counters
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: iryzhov@nfware.com
Target Milestone: ---
After running under 10G traffic over 3 days, the X710 card starts showing
incorrect RX/TX bytes statistics.
The problem seems to happen because of the following code in
i40e_update_vsi_stats:
/* exclude CRC bytes */
nes->rx_bytes -= (nes->rx_unicast + nes->rx_multicast +
nes->rx_broadcast) * ETHER_CRC_LEN;
The rx_bytes counter in X710 cards is 48-bit long, so it takes around 3 days to
overflow. When it overflows, it becomes less than (rx_pkts * ETHER_CRC_LEN),
and the substruction makes it a negative number, or, to be more precise, a very
big positive number, as it's uint64_t.
For XL710 40G cards, it will take less than one day to face the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-08-07 15:36 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-521-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.