From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Kyle Larose <eomereadig@gmail.com>, Igor Ryzhov <iryzhov@arccn.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] IXGBE error statistics
Date: Tue, 27 Oct 2015 10:26:02 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6128282A1@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA612811CC0@IRSMSX102.ger.corp.intel.com>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Van Haaren, Harry
> I'll look into it [mspdc error register stats], and post back later.
Hi guys,
Attempts to generate a 32 byte packet and make mspdc increment have not been successful - however from the datasheet and a theoretical point-of-view, it makes sense to add mspdc to rx_errors. Hence I've sent a patch that will include mspdc in the rx error count:
http://dpdk.org/dev/patchwork/patch/8064/
Thanks, -Harry
prev parent reply other threads:[~2015-10-27 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 21:23 Igor Ryzhov
2015-09-18 8:04 ` Van Haaren, Harry
2015-09-18 12:03 ` Igor Ryzhov
2015-09-21 13:45 ` Van Haaren, Harry
2015-09-21 14:09 ` Igor Ryzhov
2015-09-21 14:17 ` Kyle Larose
2015-09-21 14:22 ` Van Haaren, Harry
2015-10-27 10:26 ` Van Haaren, Harry [this message]
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=E923DB57A917B54B9182A2E928D00FA6128282A1@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=eomereadig@gmail.com \
--cc=iryzhov@arccn.ru \
/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).