From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
Cc: dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Printing statistics on running passthrough pipeline in ip_pipeline application
Date: Fri, 21 Apr 2017 12:02:44 +0530 [thread overview]
Message-ID: <CAGSp03=RNsPW9JfmSpbC0t-vMsrbo8ovFcgKdeo+u1dtukVPQw@mail.gmail.com> (raw)
In-Reply-To: <CAAx9ALWS0WC77i52AOWCzkmioVsevddaG8FuQJEYWMyvenrDSw@mail.gmail.com>
Enable flags in dpdk/config/common_base and recompile
CONFIG_RTE_*_STATS_COLLECT=y
{* for PIPELINE,PORT,TABLE ...}
On Fri, Apr 21, 2017 at 11:58 AM, Nidhia Varghese <
nidhiavarghese93@gmail.com> wrote:
> Hi,
>
> I am running ip_pipeline application using ip_pipeline.cfg file. How can I
> see the statistics of the packets that is being sent and received from this
> pipeline?
>
> I tried running as shown below:
>
> pipeline> p 1 port in 0 enable
> pipeline> p 1 port in 1 enable
> pipeline> p 1 stats port in 1
> Pipeline 1 - stats for input port 1:
> Pkts in: 0
> Pkts dropped by AH: 0
> Pkts dropped by other: 0
> 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 1 stats port out 0
> Pipeline 1 - stats for output port 0:
> Pkts in: 0
> Pkts dropped by AH: 0
> Pkts dropped by other: 0
> pipeline> p 1 stats port out 1
> Pipeline 1 - stats for output port 1:
> Pkts in: 0
> Pkts dropped by AH: 0
> Pkts dropped by other: 0
>
> I can see the packet being received and forwarded using wireshark. But not
> able to see in the statistics. Isn't this the right command to use?
>
> Thanks for your reply and help.
>
> Regards,
> Nidhia Varghese
>
prev parent reply other threads:[~2017-04-21 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 6:28 [dpdk-users] " Nidhia Varghese
2017-04-21 6:32 ` Shyam Shrivastav [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='CAGSp03=RNsPW9JfmSpbC0t-vMsrbo8ovFcgKdeo+u1dtukVPQw@mail.gmail.com' \
--to=shrivastav.shyam@gmail.com \
--cc=dev@dpdk.org \
--cc=nidhiavarghese93@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).