DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Chris Hall <chris.hall@stackpath.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] PKTGEN option to limit sending packets per second
Date: Mon, 3 Apr 2017 17:30:54 +0000	[thread overview]
Message-ID: <FAAF3280-AEC2-4E47-9814-22E3375CA479@intel.com> (raw)
In-Reply-To: <MWHPR10MB1453B5C49A8D50FB4A404D0792080@MWHPR10MB1453.namprd10.prod.outlook.com>


> On Apr 3, 2017, at 11:59 AM, Chris Hall <chris.hall@stackpath.com> wrote:
> 
> Hello,
> 
> We are doing various tests using dpdk-pktgen. One thing we were looking at is sending a consent stream of packets at a specified number of pps over a period of time. Was wondering if this could be an added feature ? something like “set 0 pps N” ?  I’ve played with the rate/burst delay, etc.. but I can’t really put a cap on packets per second.

I have not thought about rate at PPS, but it is a good idea. I do not think it will be hard to do at least I do not think so :-)

At this time I send a burst of packets up to 32 at a time using an interval or cycles. Did you really want the packets spaced equally over the second or do you want the burst of packets to be used in the calculations. At very low PPS it is possible to have 1 packet per second. The reason for the burst size is to get the best performance, but if we space the single packets across time then getting to wire rate maybe hard.

> 
> Thanks much
> Chris
> 
> 

Regards,
Keith


  reply	other threads:[~2017-04-03 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 16:59 Chris Hall
2017-04-03 17:30 ` Wiles, Keith [this message]
2017-04-03 18:02   ` Chris Hall
2017-04-03 18:58     ` Wiles, Keith
2017-04-04 22:58 Chris Hall

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=FAAF3280-AEC2-4E47-9814-22E3375CA479@intel.com \
    --to=keith.wiles@intel.com \
    --cc=chris.hall@stackpath.com \
    --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).