From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Igor Ryzhov <iryzhov@nfware.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Virtio xstats problem
Date: Fri, 26 Feb 2016 14:29:19 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612878A7D@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <26CA3897-E24A-4B7B-918F-45679AA896E0@nfware.com>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Igor Ryzhov
> 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.
Are you sending 64 byte packets? There are no 4 bytes of CRC on virtual
interfaces, so 60 bytes per packet is OK.
> 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.
Are the packets multicast or broadcast?
It looks like one of the counters there is wrong.
> PS. Is it a common practice to count broadcast packets twice - in broadcast and multicast
> counters?
No packet should be counted twice - it must be put into one bucket of mutli, broad or unicast.
-Harry
next prev parent reply other threads:[~2016-02-26 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:56 Igor Ryzhov
2016-02-26 14:29 ` Van Haaren, Harry [this message]
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=E923DB57A917B54B9182A2E928D00FA612878A7D@IRSMSX101.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=iryzhov@nfware.com \
/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).