From: Pragash Vijayaragavan <pxv3620@rit.edu>
To: users@dpdk.org
Cc: Minseok Kwon <mxkvcs@rit.edu>, Shailesh Vajpayee <srv6224@rit.edu>
Subject: [dpdk-users] dpdk interfaces counters
Date: Wed, 30 Aug 2017 02:23:25 -0400 [thread overview]
Message-ID: <CANp7S21jPNGfqQ5KLwE6u5UEkub6xgM7gDff4XXQ41dqbZtMXw@mail.gmail.com> (raw)
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
next reply other threads:[~2017-08-30 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 6:23 Pragash Vijayaragavan [this message]
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
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=CANp7S21jPNGfqQ5KLwE6u5UEkub6xgM7gDff4XXQ41dqbZtMXw@mail.gmail.com \
--to=pxv3620@rit.edu \
--cc=mxkvcs@rit.edu \
--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).