DPDK usage discussions
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Arvind Narayanan <webguru2688@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] rte_latency_stats (metrics library)
Date: Wed, 21 Aug 2019 09:59:27 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A4B0FB1@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <CAHJJQSXR7W_s4ud61yM3n0cXJ+EVDUgBhhrL-m_oq-bqMg+e1Q@mail.gmail.com>



> -----Original Message-----
> From: Arvind Narayanan [mailto:webguru2688@gmail.com]
> Sent: Saturday, August 3, 2019 11:27 PM
> To: users <users@dpdk.org>
> Cc: Pattan, Reshma <reshma.pattan@intel.com>
> Subject: rte_latency_stats (metrics library)
> 
> Hi,
> 
> I am trying to play with latency statistics library (a wrapper around
> rte_metrics lib). Whenever I try to retrieve values using
> rte_latencystats_get(), all the stats are 0.
> Even after rte_latencystats_update() still no effect on the stats.
> 
> Does this library need NIC driver support?
> Any help would be appreciated.
> 

Hi,

Do you have the traffic coming to l2fwd application?  If not you should have traffic running from the  traffic generator.


1)If you have traffic already, then can you also cross check by trying to fetch these latency stats using rte_metrics apis  instead of latency stats apis. 
(Or) equally you can run the dpdk-proc info secondary application to show you the stats (instead of you calling latency stats get and metrics get APIs).

2) Also, In DPDK, testpmd application has been updated to initiate latency stats calculation, and to see the stats you can run dpdk-procinfo secondary application alongside. 
This is to cross check that traffic is coming to dpdk application and stats are been calculated . You can try this second method if you don’t see success with l2fwd.

You can refer tespmd and dpdk-procinfo application codes to see how this is done.

Thanks,
Reshma

      reply	other threads:[~2019-08-21  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 22:27 Arvind Narayanan
2019-08-21  9:59 ` Pattan, Reshma [this message]

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=3AEA2BF9852C6F48A459DA490692831F2A4B0FB1@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=users@dpdk.org \
    --cc=webguru2688@gmail.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).