Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1

[Martin Weiser <martin.weiser@allegro-packets.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