From: Martin Weiser <martin.weiser@allegro-packets.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: ixgbe: ierrors counter spuriously increasing in DPDK 2.1
Date: Wed, 4 Nov 2015 10:10:32 +0100 [thread overview]
Message-ID: <5639CB88.7040108@allegro-packets.com> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA61282AA3C@IRSMSX102.ger.corp.intel.com>
Hi Harry,
first of all thank you for your effort.
I have done some test with the current master (which includes you
patch). It improves the situation but does not fix it entirely. The
rx-error which showed up immediately after starting the interface is
gone since this was probably caused by mac_remote_errors. But we still
see a huge number of rx-errors although all packets are received
properly and when looking at the extended stats those come from the
rx_l3_l4_xsum_error counter.
In our setup we are dealing with lots of UDP traffic which does have the
UDP checksum set to 0 (which to my knowledge is allowed for UDP). This
traffic seems to cause those rx_l3_l4_xsum_errors. When doing the same
test with other NICs (e.g. XL710) no rx-errors are accounted.
For the generic stats interface I would prefer only packets that could
not be received to be accounted in the rx-error counter regardless of
the actual NIC. What do you think?
Regards,
Martin
On 02.11.15 18:32, Van Haaren, Harry wrote:
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Martin Weiser
>> Sent: Wednesday, October 21, 2015 9:38 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1
>> with DPDK 2.1 we are seeing the ierrors counter increasing for 82599ES
>> ports without reason. Even directly after starting test-pmd the error
>> counter immediately is 1 without even a single packet being sent to the
>> device
> Hi Martin,
>
> To dig up an old thread - I've recently experienced similar issues that the rx error count increases on 82599, so I dug into the sources and realized that the MAC fault counters were being added to the rx error count.
>
> The following patch removes the MAC local and remote fault counts from rx errors, and this has fixed the issue here:
> http://dpdk.org/dev/patchwork/patch/8525/
>
> If this issue is still open perhaps try the patch and see if it improves the situation.
>
> On a related note, I'm currently implementing extended statistics for ixgbe, which showed me that the MAC faults were the root cause of the rx increase in my case.
>
> -Harry
next prev parent reply other threads:[~2015-11-04 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:38 ixgbe: ierrors counter spuriously increasing in DPDK 2.1 Martin Weiser
2015-10-21 15:53 ` Andriy Berestovskyy
2015-10-22 7:46 ` Martin Weiser
2015-10-22 10:56 ` Andriy Berestovskyy
2015-11-02 17:32 ` Van Haaren, Harry
2015-11-04 9:10 ` Martin Weiser [this message]
2015-11-04 15:50 ` [PATCH] ixgbe: remove l3_l4_xsum_errors from rx errors Harry van Haaren
2015-11-04 16:08 ` Thomas Monjalon
2015-11-04 15:54 ` ixgbe: ierrors counter spuriously increasing in DPDK 2.1 Van Haaren, Harry
2015-11-04 16:29 ` Martin Weiser
2015-11-04 16:14 ` [PATCH v2] ixgbe: remove l3_l4_xsum_errors from rx errors Harry van Haaren
2015-11-04 16:57 ` 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=5639CB88.7040108@allegro-packets.com \
--to=martin.weiser@allegro-packets.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.