From: "Wiles, Keith" <keith.wiles@intel.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Packet Generator
Date: Thu, 15 Dec 2016 14:47:40 +0000 [thread overview]
Message-ID: <BDA31AB1-528B-400D-A847-77BEF4220613@intel.com> (raw)
In-Reply-To: <F2C4FFE6-37E1-4DAB-8890-5253AFEEC636@cloudsimple.com>
> On Dec 15, 2016, at 7:21 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>
> Hi All,
>
> Can you help me in finding how the packet in generated in l2 forwarding functions. I am not able to frame the packet. In L2 packet is Ethernet Header alone sufficient for communication?
The l2fwd example does not generate packets they are received using the rte_eth_rx_burst() routine and then forwarded to the output port. Just having L2 packet header in a frame should be enough for the l2fwd example.
>
> Thanking You,
> Param
Regards,
Keith
prev parent reply other threads:[~2016-12-15 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 13:21 Kumaraparameshwaran Rathnavel
2016-12-15 14:47 ` Wiles, Keith [this message]
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=BDA31AB1-528B-400D-A847-77BEF4220613@intel.com \
--to=keith.wiles@intel.com \
--cc=krath@cloudsimple.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).