[dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1
Martin Weiser
martin.weiser at allegro-packets.com
Thu Oct 22 09:46:05 CEST 2015
Hi Andriy,
thank you for pointing this discussion out to me. I somehow missed it.
Unfortunately it looks like the discussion stopped after Maryam made a
good proposal so I will vote in on that and hopefully get things started
again.
Best regards,
Martin
On 21.10.15 17:53, Andriy Berestovskyy wrote:
> Yes Marcin,
> The issue was discussed here:
> http://dpdk.org/ml/archives/dev/2015-September/023229.html
>
> You can either fix the ierrors in ixgbe_dev_stats_get() or implement a
> workaround in your app getting the extended statistics and counting
> out some of extended counters from the ierrors.
>
> Here is an example:
> https://github.com/Juniper/contrail-vrouter/commit/72f6ca05ac81d0ca5e7eb93c6ffe7a93648c2b00#diff-99c1f65a00658c7d38b3d1b64cb5fd93R1306
>
> Regards,
> Andriy
>
> On Wed, Oct 21, 2015 at 10:38 AM, Martin Weiser
> <martin.weiser at allegro-packets.com> wrote:
>> Hi,
>>
>> 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:
>>
>> ./testpmd -c 0xfe -n 4 -- --portmask 0x3 --interactive
>> ...
>> testpmd> show port stats all
>>
>> ######################## NIC statistics for port 0 ########################
>> RX-packets: 0 RX-missed: 0 RX-bytes: 0
>> RX-badcrc: 0 RX-badlen: 0 RX-errors: 1
>> RX-nombuf: 0
>> TX-packets: 0 TX-errors: 0 TX-bytes: 0
>> ############################################################################
>>
>> ######################## NIC statistics for port 1 ########################
>> RX-packets: 0 RX-missed: 0 RX-bytes: 0
>> RX-badcrc: 0 RX-badlen: 0 RX-errors: 1
>> RX-nombuf: 0
>> TX-packets: 0 TX-errors: 0 TX-bytes: 0
>> ############################################################################
>>
>>
>> When packet forwarding is started the ports perform normally and
>> properly forward all packets but a huge number of ierrors is counted:
>>
>> testpmd> start
>> ...
>> testpmd> show port stats all
>>
>> ######################## NIC statistics for port 0 ########################
>> RX-packets: 9011857 RX-missed: 0 RX-bytes: 5020932992
>> RX-badcrc: 0 RX-badlen: 0 RX-errors: 9011753
>> RX-nombuf: 0
>> TX-packets: 9026250 TX-errors: 0 TX-bytes: 2922375542
>> ############################################################################
>>
>> ######################## NIC statistics for port 1 ########################
>> RX-packets: 9026250 RX-missed: 0 RX-bytes: 2922375542
>> RX-badcrc: 0 RX-badlen: 0 RX-errors: 9026138
>> RX-nombuf: 0
>> TX-packets: 9011857 TX-errors: 0 TX-bytes: 5020932992
>> ############################################################################
>>
>>
>> When running the exact same test with DPDK version 2.0 no ierrors are
>> reported.
>> Is anyone else seeing strange ierrors being reported for Intel Niantic
>> cards with DPDK 2.1?
>>
>> Best regards,
>> Martin
>>
>
>
More information about the dev
mailing list