From: Jose Gavine Cueto <pepedocs@gmail.com>
To: Etai Lev-Ran <elevran@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] raw frame to rte_mbuf
Date: Tue, 12 Nov 2013 18:13:39 +0800 [thread overview]
Message-ID: <CAJ5bv6H-uYu4ZwOax8S=0DFKuveCdnxPsEqat1TDdSrPHFYgbA@mail.gmail.com> (raw)
In-Reply-To: <008701cedf8f$31b7ce90$95276bb0$@com>
I see thanks for the tip.
Cheers,
Pepe
On Tue, Nov 12, 2013 at 6:08 PM, Etai Lev-Ran <elevran@gmail.com> wrote:
> Hi Pepe,
>
> In addition, you may want to consider the frame's lifetime, to ensure
> memory
> is used and released
> in a valid way.
> When sending, it may be de-referenced by DPDK and consequently a memory
> free
> may be tried.
> Hence, it is important that the raw buffer used for the ARP packet is
> allocated with a
> reference added (or, alternately, just add-ref to the packet and ensure
> it'll not be freed by DPDK
> directly).
>
> Regards,
> Etai
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Prashant Upadhyaya
> Sent: Tuesday, November 12, 2013 11:15 AM
> To: Jose Gavine Cueto; dev@dpdk.org
> Subject: Re: [dpdk-dev] raw frame to rte_mbuf
>
> 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.
>
> ============================================================================
> ===
>
>
--
To stop learning is like to stop loving.
prev parent reply other threads:[~2013-11-12 10:12 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
2013-11-12 10:08 ` Etai Lev-Ran
2013-11-12 10:13 ` Jose Gavine Cueto [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='CAJ5bv6H-uYu4ZwOax8S=0DFKuveCdnxPsEqat1TDdSrPHFYgbA@mail.gmail.com' \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.org \
--cc=elevran@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).