From: "Etai Lev-Ran" <elevran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "'Jose Gavine Cueto'" <pepedocs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: raw frame to rte_mbuf
Date: Tue, 12 Nov 2013 12:08:42 +0200 [thread overview]
Message-ID: <008701cedf8f$31b7ce90$95276bb0$@com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFDC28C6-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
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-VfR2kkLFssw@public.gmane.org] On Behalf Of Prashant Upadhyaya
Sent: Tuesday, November 12, 2013 11:15 AM
To: Jose Gavine Cueto; dev-VfR2kkLFssw@public.gmane.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-VfR2kkLFssw@public.gmane.org] On Behalf Of Jose Gavine Cueto
Sent: Tuesday, November 12, 2013 1:49 PM
To: dev-VfR2kkLFssw@public.gmane.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 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 8:19 raw frame to rte_mbuf Jose Gavine Cueto
[not found] ` <CAJ5bv6GyqHYvLUmEkKKDNvQ9-avNyMgb-SETdQp6q8pqNfba2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-12 9:15 ` Prashant Upadhyaya
[not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFDC28C6-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-12 10:08 ` Etai Lev-Ran [this message]
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='008701cedf8f$31b7ce90$95276bb0$@com' \
--to=elevran-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=pepedocs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.