From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Posadas, Emerson" <emerson.posadas@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] pktgen counters not
Date: Mon, 20 Jun 2016 17:23:11 +0000 [thread overview]
Message-ID: <3FB6384F-5F8B-43B1-8FED-DF310DDF3BED@intel.com> (raw)
Most of the counters come from the NIC hardware, but I have to do the different sizes in software. If the packet was received then it will get counted as that works in my machine and many others. Unless I broke something in Pktgen it would mean to me that the packets are not getting received by the hardware or something else is going on.
Regards,
Keith
On 6/20/16, 4:16 PM, "dev on behalf of Posadas, Emerson" <dev-bounces@dpdk.org on behalf of emerson.posadas@intel.com> wrote:
>Hello
>
>I'm running the pktgen application to do some benchmarking. My current issue with pktgen is that I don't get any packet counted against the packet size on the application even after sending some traffic.
>
> Flags:Port : P--------------:0 P--------------:1
>Link State : <UP-10000-FD> <UP-10000-FD> ----TotalRate----
>Pkts/s Max/Rx : 0/0 0/0 0/0
> Max/Tx : 14194206/0 14194254/0 28388460/0
>MBits/s Rx/Tx : 0/0 0/0 0/0
>Broadcast : 0 0
>Multicast : 0 0
> 64 Bytes : 0 0
> 65-127 : 0 0
> 128-255 : 0 0
> 256-511 : 0 0
> 512-1023 : 0 0
> 1024-1518 : 0 0
>
>I'm using DPDK 16.04 with pktgen 3.0.00 and using the following pktgen configuration flags:
>./app/app/x86_64-native-linuxapp-gcc/app/pktgen -c 0x1ff -n 2 -- -P -m "[1-4].0, [5-8].1"
>
>My NIC device is a dual port 10GbE Intel Corporation 82599EB PCIe card.
>
>EP
>
>
next reply other threads:[~2016-06-20 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:23 Wiles, Keith [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-20 14:16 Posadas, Emerson
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=3FB6384F-5F8B-43B1-8FED-DF310DDF3BED@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=emerson.posadas@intel.com \
/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).