From: "Wiles, Keith" <keith.wiles@intel.com>
To: Sara Gittlin <sara.gittlin@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen w pcap file
Date: Wed, 10 Jul 2019 13:19:02 +0000 [thread overview]
Message-ID: <117A28F3-51CD-4A6B-9BC1-6EC14F346147@intel.com> (raw)
In-Reply-To: <CAA_4wjY-PPYEf0fuH=3xBW7=d5DeEoHdRTdZKeoj93s6KQae_Q@mail.gmail.com>
The way Pktgen works is it loads the packets into memory until it fills up the number of buffers allocated, which I think is 8192 buffers. If you pcap file is more then that they are ignored.
Pktgen has different modes for the transmitting packets, the PCAP is loaded and assign to a port, but it doe not mean they will be sent. The default mode is single packet mode and you have to enable PCAP file to be sent using the enable <portlist> pcap command. Then you have to do a start <portlist> on that port to send the pcap files. Each mode has its own set of buffers it can send, so you can switch to modes and be able to reenable pcap mode on a port to send the pcap buffers again.
The pcap data loaded into memory will be sent over and over if you send more than the number of pcap packets you loaded. The way DPDK works it possible they will be send out of order :-(
> On Jul 10, 2019, at 8:12 AM, Sara Gittlin <sara.gittlin@gmail.com> wrote:
>
> Hi all
> I'm running the pkgen w pcap file , -s P:http.pcap
> but i dont see any pkts in the receive side
> Is pktgen automatically transmits the pcap after startup ? or i have to
> manually run it from the cli ?
> is it possible to run this pcap many times?
> Thank you
> -Sara
Regards,
Keith
next prev parent reply other threads:[~2019-07-10 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 13:12 Sara Gittlin
2019-07-10 13:19 ` Wiles, Keith [this message]
2019-07-10 13:41 ` Sara Gittlin
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=117A28F3-51CD-4A6B-9BC1-6EC14F346147@intel.com \
--to=keith.wiles@intel.com \
--cc=sara.gittlin@gmail.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).