From: Igor Ryzhov <iryzhov@nfware.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Virtio xstats problem
Date: Fri, 26 Feb 2016 16:56:09 +0300 [thread overview]
Message-ID: <26CA3897-E24A-4B7B-918F-45679AA896E0@nfware.com> (raw)
Hello.
I found some problem with virtio xstats counters.
Example:
rx_good_packets: 3
rx_good_bytes: 180
rx_errors: 0
rx_q0_good_packets: 3
rx_q0_good_bytes: 180
rx_q0_errors: 0
rx_q0_multicast_packets: 3
rx_q0_broadcast_packets: 1
rx_q0_undersize_packets: 3
It means that undersize packets are counted as good packets instead of errors. Or maybe size of packet is calculated wrong.
I don't have time now to check it more deeply - I can do it sometime later, but maybe someone want to help.
PS. Is it a common practice to count broadcast packets twice - in broadcast and multicast counters?
Best regards,
Igor
next reply other threads:[~2016-02-26 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:56 Igor Ryzhov [this message]
2016-02-26 14:29 ` Van Haaren, Harry
2016-02-26 14:35 ` Igor Ryzhov
2016-02-26 15:03 ` Igor Ryzhov
2016-02-26 15:18 ` Kyle Larose
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=26CA3897-E24A-4B7B-918F-45679AA896E0@nfware.com \
--to=iryzhov@nfware.com \
--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).