From: Matthew Hall <mhall@mhcomputing.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PKTGEN] dumb question: how to start packet TX and set the payload
Date: Wed, 20 Jan 2016 22:15:35 -0800 [thread overview]
Message-ID: <56A07787.2040807@mhcomputing.net> (raw)
Hello,
I was trying to just use the default PKT file, test/set_seq.pkt, like so:
sudo "./app/app/${RTE_TARGET}/pktgen" \
-l 2,3 \
--master-lcore 2 \
-n 2 \
-m 1024 \
-w 0a:00.1 \
--no-shconf \
--file-prefix pktgen \
-- \
-P \
-m 2.0 \
-f test/set_seq.pkt
After pktgen loaded, the port 0 is marked as UP. So I typed "start all"
and also tried "str". Sadly, so far, it seems like I could not get this
to actually begin sending any packets. At least, no counters are
incrementing in the pktgen UI. So I wasn't sure how to make sure it is
really sending or not.
The documentation talked about many different commands available, but it
didn't specifically say how to start transmitting the packets based on
the content of your *.pkt script file.
I'm just trying to figure out what I messed up so that I can write
(another) doc patch besides the one I just sent a moment ago.
I was also curious about putting some specific payloads into the packets
in pktgen. There are many ways of configuring the packet size, but it
doesn't talk about how and where to set the packet content. This is
important for my app as its performance will go up and down depending on
if the L4-L7 data has "interesting" content inside or not.
Sincerely,
Matthew.
next reply other threads:[~2016-01-21 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 6:15 Matthew Hall [this message]
2016-01-21 15:01 ` Wiles, Keith
2016-01-21 19:01 ` Matthew Hall
2016-01-21 15:05 ` Wiles, Keith
2016-01-21 19:00 ` Matthew Hall
2016-01-21 19:44 ` Wiles, Keith
2016-01-21 20:09 ` Matthew Hall
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=56A07787.2040807@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@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).