DPDK usage discussions
 help / color / mirror / Atom feed
From: James Bensley <jwbensley@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] PktGen Ethertype
Date: Wed, 10 May 2017 10:09:29 +0100	[thread overview]
Message-ID: <CAAWx_pVXMxLKXNoREm-i=GmOP1vZTDrkUER-rQ8PqsQKcyN4Mg@mail.gmail.com> (raw)
In-Reply-To: <B59FD1B0-D2D4-49EA-9C21-D3B2E0A47EFE@intel.com>

On 9 May 2017 at 14:56, Wiles, Keith <keith.wiles@intel.com> wrote:

Hi Keith!

> The range command can allow you to adjust the type field and then send those in a burst. The problem is pktgen was designed to send packets at a high rate if needed and that means setting up the packets before hand. The number of packets being able to be setup before hand is 8192. The random command can adjust the ether type randomly for each packet with a performance hit. Maybe one of these would help.

So it sounds like the range command is what I want then, if I can
systematically adjust the EtherType field (e.g. I can explicitly say
start at 0x0 and run to 0xFFFF) just with the caveat that I have to
send a burst of packet for each loop iteration?

If that is the case I don't mind, it will still get the job done of
testing every Ethertype through a DUT. Any chance I can lower the
burst size on the CLI to 64 packets for example to speed things up?

> Also I am more then willing to take patches :-)

Sure, I didn't want to spend hours testing to find out that I can't do
what I wanted to do which is why I asked here.

Sounds like it can be done so I'll have a poke around with the code
and see what I can do.

Thanks for your help it is greatly appreciated,
James.

  parent reply	other threads:[~2017-05-10  9:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  8:55 James Bensley
2017-05-09 13:56 ` Wiles, Keith
2017-05-09 14:13   ` Paul Emmerich
2017-05-10  9:12     ` James Bensley
2017-05-10  9:09   ` James Bensley [this message]
2017-05-10 13:53     ` Wiles, Keith

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='CAAWx_pVXMxLKXNoREm-i=GmOP1vZTDrkUER-rQ8PqsQKcyN4Mg@mail.gmail.com' \
    --to=jwbensley@gmail.com \
    --cc=keith.wiles@intel.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).