From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
To: users <users@dpdk.org>
Subject: stats inconsistency
Date: Thu, 6 Feb 2025 11:14:57 +0530 [thread overview]
Message-ID: <CACh--shn7pUxga0Uhe96wCJDsbTne-ZcRgpbCeConB4MtJFaRg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hello,
I was trying to send packets on one interface and capture on another
interface both connected b2b without any DUT in between.
While sending packets, the value returned by rte_eth_tx_burst is not
consistent with opackets / oerrors returned by rte_eth_stats_get even after
a few seconds.
None of port 0 Tx stats are consistent with port 1 Rx stats stats.
The value returned by rte_eth_rx_burst is consistent with ipackets.
Still ipackets/ierrors/imissed of port 1 are not consistent with
opackets/oerrors of port 0.
Is there a way to achieve consistency among all ?
Thanks & Regards
--
Lokesh Chakka.
[-- Attachment #2: Type: text/html, Size: 1007 bytes --]
reply other threads:[~2025-02-06 5:45 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=CACh--shn7pUxga0Uhe96wCJDsbTne-ZcRgpbCeConB4MtJFaRg@mail.gmail.com \
--to=lvenkatakumarchakka@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).