From: Yerden Zhumabekov <e_zhumabekov@sts.kz>
To: Panu Matilainen <pmatilai@redhat.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] random pkt generator PMD
Date: Wed, 15 Jun 2016 18:14:34 +0600 [thread overview]
Message-ID: <576146AA.2030108@sts.kz> (raw)
In-Reply-To: <cf65c372-b2aa-8d44-98db-dcbf8a02ecb4@redhat.com>
On 15.06.2016 17:25, Panu Matilainen wrote:
> On 06/15/2016 02:10 PM, Yerden Zhumabekov wrote:
>>
>>
>> On 15.06.2016 16:43, Dumitrescu, Cristian wrote:
>>>
>>>>
>>>> Hello everybody,
>>>>
>>>> DPDK already got a number of PMDs for various eth devices, it even has
>>>> PMD emulations for backends such as pcap, sw rings etc.
>>>>
>>>> I've been thinking about the idea of having PMD which would generate
>>>> mbufs on the fly in some randomized fashion. This would serve goals
>>>> like, for example:
>>>>
>>>> 1) running tests for applications with network processing capabilities
>>>> without additional software packet generators;
>>>> 2) making performance measurements with no hw inteference;
>>>> 3) ability to run without root privileges, --no-pci, --no-huge, for CI
>>>> build, so on.
>>>>
>>>> Maybe there's no such need, and these goals may be achieved by other
>>>> means and this idea is flawed? Any thoughts?
>>> How about a Perl/Python script to generate a PCAP file with random
>>> packets and then feed the PCAP file to the PCAP PMD?
>>>
>>> Random can mean different requirements for different
>>> users/application, I think it is difficult to fit this under a simple
>>> generic API. Customizing the script for different requirements if a
>>> far better option in my opinion.
>>
>> AFAIK, the thing about pcap pmd is that one needs to rewind pcap file
>> once pcap pmd reaches its end. It requires additional (non-generic)
>> handling in app code.
>
> So add a loop-mode to pcap pmd?
It would be nice to have an option like "...,rewind=1,...".
next prev parent reply other threads:[~2016-06-15 12:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 9:43 Yerden Zhumabekov
2016-06-15 9:49 ` Bruce Richardson
2016-06-15 10:03 ` Yerden Zhumabekov
2016-06-15 10:07 ` Bruce Richardson
2016-06-21 8:43 ` Yerden Zhumabekov
2016-06-15 10:43 ` Dumitrescu, Cristian
2016-06-15 11:10 ` Yerden Zhumabekov
2016-06-15 11:25 ` Panu Matilainen
2016-06-15 12:14 ` Yerden Zhumabekov [this message]
2016-06-15 12:24 ` Panu Matilainen
2016-06-15 12:25 ` Dumitrescu, Cristian
2016-06-15 12:54 ` Yerden Zhumabekov
2016-06-15 13:03 ` Dumitrescu, Cristian
2016-06-15 13:30 ` Arnon Warshavsky
2016-06-15 11:25 ` Dumitrescu, Cristian
2016-06-15 12:11 ` Dumitrescu, Cristian
2016-06-15 11:40 ` Thomas Monjalon
2016-06-15 11:48 ` Mcnamara, John
2016-06-15 11:50 ` Jay Rolette
2016-06-15 12:11 ` Yerden Zhumabekov
2016-06-15 12:33 ` Jay Rolette
2016-06-15 12:48 ` Yerden Zhumabekov
2016-06-15 13:02 ` Neil Horman
2016-06-16 6:20 ` Yerden Zhumabekov
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=576146AA.2030108@sts.kz \
--to=e_zhumabekov@sts.kz \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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).