On 04.11.15 16:54, Van Haaren, Harry wrote:
>> From: Martin Weiser [mailto:martin.weiser at allegro-packets.com]
>> Subject: Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK
>> 2.1
>> The
>> rx-error which showed up immediately after starting the i
> From: Martin Weiser [mailto:martin.weiser at allegro-packets.com]
> Subject: Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK
> 2.1
> The
> rx-error which showed up immediately after starting the interface is
> gone since this was probably caused by
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 at dpdk.org] On Behalf Of Martin Weiser
>> Sent: Wednesday, October 21, 2015 9:38 AM
>> To: dev at dpdk.org
>> Subject: [dpdk-dev
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Martin Weiser
> Sent: Wednesday, October 21, 2015 9:38 AM
> To: dev at 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
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
wrote:
> Hi Andriy,
>
> thank you for pointing this discussion out to m
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 w
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 a
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
8 matches
Mail list logo