From: "Wiles, Keith" <keith.wiles@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] dumb question: how to start packet TX and set the payload
Date: Thu, 21 Jan 2016 19:44:21 +0000 [thread overview]
Message-ID: <88FD4A1B-A860-4488-96E0-28D6C544204B@intel.com> (raw)
In-Reply-To: <20160121190037.GB10170@mhcomputing.net>
On 1/21/16, 1:00 PM, "Matthew Hall" <mhall@mhcomputing.net> wrote:
>On Thu, Jan 21, 2016 at 03:05:38PM +0000, Wiles, Keith wrote:
>> Forgot to answer this one. Pktgen does not allow the user to define the
>> content of the packet per say only the fill pattern and what ever you
>> configure the packet type to be. If you would like to submit a patch for
>> adding user specific content it has always been a goal of my to add that
>> feature.
>
>I am happy to work to make the patch, it would help if you could provide some
>hints where in the code I should look... when I went searching for seqCnt I
>found a packet-constructor function run in a loop when applying a
>packet-sequence operation. Is the packet-constructor the right place or should
>I look somewhere else?
The packet-constructor builds the different types single, range, sequence and PCAP packets, before the packets are sent.
What type of data do you want to add to the packets? Now it builds IPv4/UDP/TCP packets, do you need to replace UDP or TCP or just add more protocol layers?
>
>Matthew.
>
Regards,
Keith
next prev parent reply other threads:[~2016-01-21 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 6:15 Matthew Hall
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 [this message]
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=88FD4A1B-A860-4488-96E0-28D6C544204B@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).