From: Nulik Nol <nuliknol-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: how to find transfer rate ?
Date: Sat, 1 Jun 2013 08:38:17 -0500 [thread overview]
Message-ID: <CAHO6xe8zYSAV1uqvnbYC8hPH2UbvdpFZzoChorpARPDoxkemQw@mail.gmail.com> (raw)
Hi all,
I finally bought my Intel NIC (an I340-T2,
E1000_DEV_ID_82580_COPPER_DUAL, dev id 0x150E) and ran the dpdk with
success. But when testing the cards for speed rate with "testpmd"
program provided in the distribution I can't find the Packets Per
Second rate, the statistics reported do not show start and end time,
so I can't calculate how much packets were transferred. How do you get
this value ?
Thanks in advance
Nulik
next reply other threads:[~2013-06-01 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 13:38 Nulik Nol [this message]
[not found] ` <CAHO6xe8zYSAV1uqvnbYC8hPH2UbvdpFZzoChorpARPDoxkemQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-03 7:05 ` how to find transfer rate ? Ivan Boule
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=CAHO6xe8zYSAV1uqvnbYC8hPH2UbvdpFZzoChorpARPDoxkemQw@mail.gmail.com \
--to=nuliknol-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).