From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "users@dpdk.org" <users@dpdk.org>,
"sridhariyer@versa-networks.com" <sridhariyer@versa-networks.com>
Subject: Re: [dpdk-users] e1000 port stats
Date: Mon, 30 Nov 2015 12:18:40 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA61283BB83@IRSMSX102.ger.corp.intel.com> (raw)
> Hi,
Hi Sridhar,
> In DPDK/lib/librte_pmd_e1000/em_ethdev.c:889 (eth_em_stats_get), for some reason, ibytes and obytes are not getting update, ipackets/opackets seem to be fine (kvm using e1000)
I've recently sent some patches regarding stats for the e1000 PMD.
> (gdb) p *rte_stats
> $3 = {ipackets = 228635, opackets = 350, ibytes = 0, obytes = 0, imissed = 0, ibadcrc = 0, ibadlen = 0, ierrors =
The following commit in git fixed the issue you are experiencing:
67b38d9 e1000: fix total byte statistics
> This works fine on esxi guests using e1000.
I presume you are passing a VF to esxi? The igbvf PMD has a different stats_get() function to the igb PF PMD, so the bug would not be visible there.
> I'm using dpdk 1.7. Any pointers would be great.
As stated, Git includes the fix, along with some more updates like providing extended statistics via the xstats_get() API.
The commit mentioned above is a small code-change and fixes your immediate bug - it will probably apply cleanly to 1.7, otherwise it's an easy backport.
-Harry
next reply other threads:[~2015-11-30 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 12:18 Van Haaren, Harry [this message]
2015-11-30 21:06 ` Sridhar.V.Iyer
2015-12-08 10:54 ` Van Haaren, Harry
2015-12-08 18:52 ` Sridhar.V.Iyer
2015-12-10 0:12 ` Sridhar.V.Iyer
-- strict thread matches above, loose matches on Subject: below --
2015-11-19 2:11 Sridhar.V.Iyer
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=E923DB57A917B54B9182A2E928D00FA61283BB83@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=sridhariyer@versa-networks.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).