Re: [dpdk-dev] [PATCH] examples: new txburst application

["Wiles, Keith" <keith.wiles@intel.com>]

On 1/30/15, 1:45 PM, "Wiles, Keith" <keith.wiles@intel.com> wrote:

>
>
>Sent from my iPhone
>
>On Jan 30, 2015, at 9:49 AM, Bhavesh Davda <bhavesh@vmware.com> wrote:
>
>>> Did you know pktgen-dpdk?
>>> http://dpdk.org/browse/apps/pktgen-dpdk/tree/README.md
>>> 
>>> Do you think it could replace your application?
>> 
>> [Bhavesh Davda] Yes, I regularly use pktgen-dpdk, and love the app
>>(thanks Keith!) but I couldn't quite get it to do this simplistic job of
>>generating a stream of X-byte UDP packets in burst of Y spread apart by
>>Z microseconds.
>
>Hmmm, sounds like an enhancement request to pktgen is needed here. I will
>look at adding it to pktgen and it is up to everyone if the example is
>reasonable to have. For me it does seem reasonable to include as it maybe
>simpler to setup, but if and when I can add that support to pktgen it may
>no longer be needed.
>
>Let me have a look at adding the support and will let you guys know next
>week.

Looking at the txburst code and your description needing to send a burst
of 220 byte UDP packets with an interval of 50us is mostly doable via
Pktgen. In Pktgen you can setup a packet 220+UDP+other parameters already
in single packet mode or sequence mode. You can set the rate at a given
percentage per second of packets, but you can not set the interval rate
between burst easily. The number of packets in a burst is also adjustable
via the burst command ¹set <portlist> burst <value>'.

Did I describe the problem here correctly?

The current percentage rate is in whole numbers in Pktgen may not be fine
enough gain rate for some tests. I do have in Pktgen a way to adjust the
time between burst of packets using a debug command to fine tune the
number of clock ticks (HPET) to a given number ¹set <portlist> tx_cycles
<value>', would that command be useful and solve your given test case?

The tx_cycles option is not listed in the help text :-) Maybe I should
make it not hidden.

>
>Thanks Keith