DPDK usage discussions
 help / color / mirror / Atom feed
From: Pragash Vijayaragavan <pxv3620@rit.edu>
To: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Cc: Andriy Berestovskyy <aber@semihalf.com>, users <users@dpdk.org>,
	Minseok Kwon <mxkvcs@rit.edu>,
	Shailesh Vajpayee <srv6224@rit.edu>
Subject: Re: [dpdk-users] dpdk interfaces counters
Date: Wed, 30 Aug 2017 18:10:13 -0400	[thread overview]
Message-ID: <CANp7S21JQ=4uZHMHgpjYL5sQSq8tpa11HLrpj75x2WVqjF0jCw@mail.gmail.com> (raw)
In-Reply-To: <CAGSp03nXH9WbKMewSTCjt+kQU9TqzFwiPiYeP96QkoobKU8hoQ@mail.gmail.com>

Thanks for the inputs.

We use MoonGen to generate traffic. We will let you know if we face more
issues.

Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Wed, Aug 30, 2017 at 6:21 AM, Shyam Shrivastav <
shrivastav.shyam@gmail.com> wrote:

> Yes rte_eth_stats_get() work by default, CONFIG_RTE_PORT_STATS_COLLECT
> enables port stats in librte_port layer ..
>
> On Wed, Aug 30, 2017 at 3:29 PM, Andriy Berestovskyy <aber@semihalf.com>
> wrote:
>
>> rte_eth_stats_get() works fine by default.
>>
>> Andriy
>>
>> On Wed, Aug 30, 2017 at 11:24 AM, Shyam Shrivastav
>> <shrivastav.shyam@gmail.com> wrote:
>> > Also port stats need to  be enabled in common config
>> >
>> > common_base:CONFIG_RTE_LIBRTE_ARK_DEBUG_STATS=n
>> > common_base:CONFIG_RTE_LIBRTE_JOBSTATS=y
>> > common_base:CONFIG_RTE_LIBRTE_LATENCY_STATS=y
>> > common_base:CONFIG_RTE_SCHED_COLLECT_STATS=n
>> > common_base:CONFIG_RTE_PORT_STATS_COLLECT=n
>> > common_base:CONFIG_RTE_TABLE_STATS_COLLECT=n
>> > common_base:CONFIG_RTE_PIPELINE_STATS_COLLECT=n
>> > common_base:CONFIG_RTE_TEST_PMD_RECORD_BURST_STATS=n
>> >
>> >
>> > On Wed, Aug 30, 2017 at 2:49 PM, Andriy Berestovskyy <aber@semihalf.com
>> >
>> > wrote:
>> >>
>> >> Hey,
>> >> Have a look at rte_eth_stats_get():
>> >>
>> >> http://dpdk.org/doc/api/rte__ethdev_8h.html#a97567472450b31e
>> f53950fb2ef47298b
>> >>
>> >> Andriy
>> >>
>> >> On Wed, Aug 30, 2017 at 8:23 AM, Pragash Vijayaragavan <
>> pxv3620@rit.edu>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I have 2 NICs connected to dpdk, I send traffic from 1 and receive on
>> >> > the
>> >> > other.
>> >> >
>> >> > Is there anyway how i can see the interface counters of these NICs to
>> >> > check
>> >> > whether my packets are received.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Pragash Vijayaragavan
>> >> > Grad Student at Rochester Institute of Technology
>> >> > email : pxv3620@rit.edu
>> >> > ph : 585 764 4662
>> >>
>> >>
>> >>
>> >> --
>> >> Andriy Berestovskyy
>> >
>> >
>>
>>
>>
>> --
>> Andriy Berestovskyy
>>
>
>

      reply	other threads:[~2017-08-30 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  6:23 Pragash Vijayaragavan
2017-08-30  6:32 ` Muhammad Zain-ul-Abideen
2017-08-30  9:19 ` Andriy Berestovskyy
2017-08-30  9:24   ` Shyam Shrivastav
2017-08-30  9:59     ` Andriy Berestovskyy
2017-08-30 10:21       ` Shyam Shrivastav
2017-08-30 22:10         ` Pragash Vijayaragavan [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='CANp7S21JQ=4uZHMHgpjYL5sQSq8tpa11HLrpj75x2WVqjF0jCw@mail.gmail.com' \
    --to=pxv3620@rit.edu \
    --cc=aber@semihalf.com \
    --cc=mxkvcs@rit.edu \
    --cc=shrivastav.shyam@gmail.com \
    --cc=srv6224@rit.edu \
    --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).