Re: [dpdk-dev] Port stats zero when using MLX5 DPDK driver

[Shahaf Shuler <shahafs@mellanox.com>]

supporting this functionality is not on the plans. If you wish to read statistics of a running process you can use ethtool –S <device_name>.
It will provide you the statistics of the port.
Note that those statistics count the number of bytes/packet which were received/sent by the port. This number may not be equal to the number of packet/bytes which were send/received on the PMD.

--Shahaf

From: george.dit@gmail.com [mailto:george.dit@gmail.com]
Sent: Monday, January 9, 2017 4:45 PM
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Port stats zero when using MLX5 DPDK driver

Hi Shahaf,

Thanks for the clarification!
Is there a plan for this functionality to be provided (soon)? (or any technical limitation that stands in this way)

Thanks and best regards,
Georgios

On Mon, Jan 9, 2017 at 2:32 PM, Shahaf Shuler <shahafs@mellanox.com<mailto:shahafs@mellanox.com>> wrote:
Hi Georgios,

It is not support on Mellanox PMD to read the primary process counters from a secondary process.


--Shahaf


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>] On Behalf Of george.dit@gmail.com<mailto:george.dit@gmail.com>
Sent: Sunday, January 8, 2017 3:38 PM
To: dev@dpdk.org<mailto:dev@dpdk.org>
Subject: [dpdk-dev] Port stats zero when using MLX5 DPDK driver

Hi,

I have a simple setup with a machine that contains a dual port 10 GbE Intel 82599ES NIC and another dual port 100 GbE Mellanox ConnectX-4 NIC. The Intel ports are 0 and 1, while the Mellanox ones are 2 and 3.

I properly compiled DPDK 16.11 and test-pmd works just fine for all 4 ports.
Then, I ran a simple primary application that forwards packets from 0 <-->
1 and 2 <--> 3 and started dpdk-procinfo -- --stats (or --xstats) as a secondary monitoring process, while sending some traffic to all 4 ports.
The problem I see is that the statistics reported by the Mellanox NICs are always zero (Intel ports report just fine).

What is the reason behind this behavior? Is there a bug in the driver (maybe recently fixed by DPDK 17.02 rc?) or is it simply a lack of this functionality?

Thanks and best regards,

--
   Georgios Katsikas
   Ph.D. Student and Research Assistant
   Network Systems Lab (NSL)



       *E-Mail:*  george <george.katsikas@imdea.org<mailto:george.katsikas@imdea.org>>.dit@gmail.com<mailto:dit@gmail.com>
   *Web Site:*  http://www.di.uoa.gr/~katsikas/ <http://people.networks.imdea.org/~george_katsikas/index.html>



--
   Georgios Katsikas
   Ph.D. Student and Research Assistant
   Network Systems Lab (NSL)

   [http://www.kth.se/polopoly_fs/1.77259!/image/logo-main-2013.png]

       E-Mail:  george<mailto:george.katsikas@imdea.org>.dit@gmail.com<mailto:dit@gmail.com>
   Web Site:  http://www.di.uoa.gr/~katsikas/<http://people.networks.imdea.org/~george_katsikas/index.html>