DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andriy Berestovskyy <aber@semihalf.com>
To: Martin Weiser <martin.weiser@allegro-packets.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1
Date: Thu, 22 Oct 2015 12:56:05 +0200	[thread overview]
Message-ID: <CAOysbxqZd2iFxcc3zGisi3LDJYdNPx1uoumi5OwVS=HTkQLzhw@mail.gmail.com> (raw)
In-Reply-To: <5628943D.80401@allegro-packets.com>

Hi Martin,
We agreed on the main point: it's an issue. IMO the implementation
details are up to Maryam.

There have been few patches, so I guess it will be fixed in 2.2.

Andriy


On Thu, Oct 22, 2015 at 9:46 AM, Martin Weiser
<martin.weiser@allegro-packets.com> wrote:
> 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@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
>>>
>>
>>
>
>



-- 
Andriy Berestovskyy

  reply	other threads:[~2015-10-22 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  8:38 Martin Weiser
2015-10-21 15:53 ` Andriy Berestovskyy
2015-10-22  7:46   ` Martin Weiser
2015-10-22 10:56     ` Andriy Berestovskyy [this message]
2015-11-02 17:32 ` Van Haaren, Harry
2015-11-04  9:10   ` Martin Weiser
2015-11-04 15:50     ` [dpdk-dev] [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     ` [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1 Van Haaren, Harry
2015-11-04 16:29       ` Martin Weiser
2015-11-04 16:14     ` [dpdk-dev] [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='CAOysbxqZd2iFxcc3zGisi3LDJYdNPx1uoumi5OwVS=HTkQLzhw@mail.gmail.com' \
    --to=aber@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=martin.weiser@allegro-packets.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).