DPDK patches and discussions
 help / color / mirror / Atom feed
From: george.dit@gmail.com
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Port stats zero when using MLX5 DPDK driver
Date: Mon, 9 Jan 2017 15:44:54 +0100	[thread overview]
Message-ID: <CAN9HtFACigKN4MTZeTzAjkNXD2G3N5cSGnRaVJO6MRZOtQn5cw@mail.gmail.com> (raw)
In-Reply-To: <AM4PR05MB1505297E0C5668DD7A1B2DA6C3640@AM4PR05MB1505.eurprd05.prod.outlook.com>

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> 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] On Behalf Of george.dit@gmail.com
> Sent: Sunday, January 8, 2017 3:38 PM
> To: 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>.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)



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

  reply	other threads:[~2017-01-09 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 13:38 george.dit
2017-01-09 13:32 ` Shahaf Shuler
2017-01-09 14:44   ` george.dit [this message]
2017-01-10  8:43     ` Shahaf Shuler
2017-01-11 13:46       ` Thomas Monjalon
2017-01-12  7:34         ` Shahaf Shuler

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=CAN9HtFACigKN4MTZeTzAjkNXD2G3N5cSGnRaVJO6MRZOtQn5cw@mail.gmail.com \
    --to=george.dit@gmail.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.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).