DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Yerden Zhumabekov <e_zhumabekov@sts.kz>,
	Panu Matilainen <pmatilai@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] random pkt generator PMD
Date: Wed, 15 Jun 2016 13:03:30 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A066BF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <5761501D.9000202@sts.kz>



> -----Original Message-----
> From: Yerden Zhumabekov [mailto:e_zhumabekov@sts.kz]
> Sent: Wednesday, June 15, 2016 1:55 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Panu Matilainen
> <pmatilai@redhat.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] random pkt generator PMD
> 
> 
> 
> On 15.06.2016 18:25, Dumitrescu, Cristian wrote:
> 
> >>>> So add a loop-mode to pcap pmd?
> >>> It would be nice to have an option like "...,rewind=1,...".
> >> As Cristian points out in
> >> http://dpdk.org/ml/archives/dev/2016-June/041589.html, the current
> pmd
> >> behavior of stopping is the odd man out in the pmd crowd.
> >>
> >> Rather than whether to rewind or not, I'd make the number of loops
> >> configurable, defaulting to forever and 1 being the equal to current
> >> behavior.
> >>
> >> 	- Panu -
> > +1
> 
> I'm afraid, all packets from pcap file would need to be preloaded to
> memory. Otherwise, each loop would infer pcap_open/pcap_close(), am I
> wrong?

This exactly what the code in source port is doing.

Basically, this is optimized for the case when number of packets in the PCAP file is relatively small, so the PCAP memory footprint when loaded into memory is small so it fits the L1/L2 cache. Provides traffic generation capability when performance measurements are not key: testing, code development on your laptop while on board of a plane, simulation environments, etc.

When the PCAP is large (e.g. capture of the traffic in your local cloud for 2 mins), then PCAP memory gets swapped to disk and performance obviously drops. Still better than opening PCAC for each packet. Useful for e.g. IDS/IPS testing. 

  reply	other threads:[~2016-06-15 13:03 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
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 [this message]
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=3EB4FA525960D640B5BDFFD6A3D8912647A066BF@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=e_zhumabekov@sts.kz \
    --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).