DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: abhijit naik <abhijitnaik27@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Need information on benchmark testing using pktgen
Date: Mon, 13 Apr 2020 14:31:07 +0000	[thread overview]
Message-ID: <7D7AA108-D7AA-4487-B359-6BB0B68655AF@intel.com> (raw)
In-Reply-To: <CANaY3hPL0F49Zb0qB_5k7+0wpZiOefnp2zQ40Npxv=xYh75qDg@mail.gmail.com>



> On Apr 13, 2020, at 3:55 AM, abhijit naik <abhijitnaik27@gmail.com> wrote:
> 
> Hi All,
> 
> I am planning to use the pktgen for benchmarking one of the Ethernet
> IP. I needed some clarification w.r.t pktgen
> Whether throughput, loss and latency can be measured by point to point
> connection between test system and DUT(Without switch)?

Throughput and packet loss is done within the code, but a percentage of loss is not calculated.
Latency is a bit tricky as the sent from pktgen needs to return to the same port and CPU to get a latency number. The latency must be enabled on the port to get the value. The reason it needs to be the same port/core is the counter used is the per core timestamp register.

> If yes, then
> where should pktgen tx and rx should run?

Not sure about this question, normally pktgen run on one machine targeting the DUT, but you can run pktgen on the machine or the DUT, just a bit more complex of a setup.
> Is support for RFC-2544 test specification complete?

I have a script in the repo that tries to do rfc2544 like test, but may not the best script.
> Is their any development activity going on for RFC-2889?
No.
> 
> Thank you
> 
> -- 
> Best wishes,
> Abhijit Naik


      reply	other threads:[~2020-04-13 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  8:55 abhijit naik
2020-04-13 14:31 ` Wiles, Keith [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=7D7AA108-D7AA-4487-B359-6BB0B68655AF@intel.com \
    --to=keith.wiles@intel.com \
    --cc=abhijitnaik27@gmail.com \
    --cc=dev@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).