From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] ixgbe: remove rx jabber from ierrors
Date: Tue, 20 Oct 2015 08:30:09 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612825AFD@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC0909020A09AA@shsmsx102.ccr.corp.intel.com>
Hi Wenzhuo,
> From: Lu, Wenzhuo
> > Remove receive jabber count from ierrors count as the registers overlap,
> > previously causing some packets to be counted twice.
>
> Would you like to let us know which register RJC overlaps into? Thanks.
It seems that the RJC register overlaps with CRC errors.
Thanks for looking at this patch, -Harry
next prev parent reply other threads:[~2015-10-20 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151014163553.GB7420@bricha3-MOBL3>
2015-10-14 17:12 ` Harry van Haaren
2015-10-20 1:13 ` Lu, Wenzhuo
2015-10-20 8:30 ` Van Haaren, Harry [this message]
2015-10-20 8:49 ` Lu, Wenzhuo
2015-10-20 9:23 ` [dpdk-dev] [PATCH v3] " Harry van Haaren
2015-10-20 9:38 ` Tahhan, Maryam
2015-10-21 0:54 ` Lu, Wenzhuo
2015-10-28 14:11 ` Thomas Monjalon
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=E923DB57A917B54B9182A2E928D00FA612825AFD@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@intel.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).