From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: Jose Gavine Cueto <pepedocs@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] raw frame to rte_mbuf
Date: Tue, 12 Nov 2013 14:45:08 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFDC28C6@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <CAJ5bv6GyqHYvLUmEkKKDNvQ9-avNyMgb-SETdQp6q8pqNfba2A@mail.gmail.com>
Hi Pepe,
Ofcourse a simple cast will not suffice.
Please look the rte_mbuf structure in the header files and let me know if you still have the confusion.
There is a header and payload. Your raw frame will go in the payload.
Regards
-Prashant
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jose Gavine Cueto
Sent: Tuesday, November 12, 2013 1:49 PM
To: dev@dpdk.org
Subject: [dpdk-dev] raw frame to rte_mbuf
Hi,
In DPDK how should a raw ethernet frame converted to rte_mbuf * ? For example if I have an ARP packet:
void * arp_pkt
how should this be converted to an rte_mbuf * for transmission, does a simple cast suffice ?
Cheers,
Pepe
--
To stop learning is like to stop loving.
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next prev parent reply other threads:[~2013-11-12 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 8:19 Jose Gavine Cueto
2013-11-12 9:15 ` Prashant Upadhyaya [this message]
2013-11-12 10:08 ` Etai Lev-Ran
2013-11-12 10:13 ` Jose Gavine Cueto
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=C7CE7EEF248E2B48BBA63D0ABEEE700C45DFDC28C6@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dev@dpdk.org \
--cc=pepedocs@gmail.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).