DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Yerden Zhumabekov <e_zhumabekov@sts.kz>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] random pkt generator PMD
Date: Wed, 15 Jun 2016 11:07:01 +0100	[thread overview]
Message-ID: <20160615100701.GC10172@bricha3-MOBL3> (raw)
In-Reply-To: <5761280F.6020106@sts.kz>

On Wed, Jun 15, 2016 at 04:03:59PM +0600, Yerden Zhumabekov wrote:
> On 15.06.2016 15:49, Bruce Richardson wrote:
> >On Wed, Jun 15, 2016 at 03:43:56PM +0600, Yerden Zhumabekov 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?
> >Isn't some of this already covered by the NULL PMD? Perhaps it could be extended
> >or enhanced to meet some more of your requirements?
> >
> >/Bruce
> Right, but development of various features regarding L3/L4 etc requires more
> subtle approach, like live packets, different protocol versions, fields
> manipulation. In this case some packet mangling/randomizing capabilities
> would be quite useful. Something similar to what is done in Pktgen, but more
> lightweight approach, in a same app.
> 
> I've almost made my mind :) so the next question: is there any guide on PMD
> dev? I'm looking through rte_ether.h right now, but some doc would be very
> nice.

Unfortunately not. My suggestion is to take one of the simple vdev's e.g. ring,
pcap, null, and work off a copy of it.

/Bruce

  reply	other threads:[~2016-06-15 10:07 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 [this message]
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
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=20160615100701.GC10172@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=e_zhumabekov@sts.kz \
    /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).