DPDK usage discussions
 help / color / mirror / Atom feed
From: Heena Sirwani <heena.sirwani@nevisnetworks.com>
To: users@dpdk.org, sharanya k <ksharanya.97@gmail.com>
Subject: Re: [dpdk-users] Enabling stats in pipeline applications
Date: Thu, 8 Feb 2018 19:41:04 +0530 (IST)	[thread overview]
Message-ID: <243287365.13423.1518099064235.JavaMail.root@127.0.0.1> (raw)
In-Reply-To: <CAHJ=+w5ix18poLf8x=DpAoPpGssKKFizAAp0odOVmaCwOQYSDg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1506 bytes --]

    
     I had a similar issue. The problem turned out to be in configs.
Make sure the configuration changes are made in the target in $RTE_SDK/$RTE_TARGET/.config.
Either edit that config file for build local configs or remake target configuration by

make config T=$RTE_TARGET
-- Original Message --
 
From: sharanya k [ksharanya.97@gmail.com]
To: [users@dpdk.org]
Date: Thu 08 February 2018 [6:45:13 PM]
Subject: [dpdk-users] Enabling stats in pipeline applications
Hi,
I am running an ip pipeline application in dpdk version 17.08.1
(stable). I can see the packets getting received and send through
Wireshark. But, I couldn't get the statistics in the pipeline app
using the following command.
pipeline> p 1 stats port in 0
Pipeline 1 - stats for input port 0:
Pkts in: 0
Pkts dropped by AH: 0
Pkts dropped by other: 0
pipeline> p 2 stats port in 0
Pipeline 2 - stats for input port 0:
Pkts in: 0
Pkts dropped by AH: 0
Pkts dropped by other: 0
pipeline> p 2 stats port out 0
Pipeline 2 - stats for output port 0:
Pkts in: 0
Pkts dropped by AH: 0
Pkts dropped by other: 0
I even enabled the following flags in dpdk/config/common_base and recompiled.
CONFIG_RTE_*_STATS_COLLECT=y
Still its not working.
Can you please help me to rectify this?
Regards,
Sharanya\x16º&™«m…ì\x1c¢šh•® ™¨¥r‰“†á^oÍ{çn{ÛM|Eën®sÚ¶\x19š¶Ø^ÁÊ)¦‰Zâ	šŠW(™\x17œz+Þuúèšf¢–‹t\x7f^õ‚Š •ç(šf¢–‹t\x7f^õ‚Š •ç(›¾5ÛŸ6×½[ÉÚ]’Šà>‹-~,pŠØDHÄωß\x04\00µ\aÍz~Šî±êìv—d¢¸\x13†ï\x05y½´×Í{çn{ûMtÐ!\x13Eç\x1eŠ÷o)šŠZ-Ñý{Ö
(‚Wœ¢l"¶\x14ŒLøk»(ãÝõÛÞh¶O_¢»¬z»\x1d¥Ù(®\x04á»O\x05y½´×Í<çn{ÓÍ4=$Ã(ƒ\x12Š	Ú¶êÞ

  reply	other threads:[~2018-02-08 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 13:15 sharanya k
2018-02-08 14:11 ` Heena Sirwani [this message]
2018-02-09 12:24   ` sharanya k
2018-02-09 13:07     ` Heena Sirwani

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=243287365.13423.1518099064235.JavaMail.root@127.0.0.1 \
    --to=heena.sirwani@nevisnetworks.com \
    --cc=ksharanya.97@gmail.com \
    --cc=users@dpdk.org \
    /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).