From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jose Gavine Cueto <pepedocs@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_mbuf - contiguous ?
Date: Thu, 24 Oct 2013 10:32:14 +0200 [thread overview]
Message-ID: <201310241032.14803.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CAJ5bv6GVAJ_W+iQvVtDGVqExEqUAnrh9Dg1noNUhX0=Abgme-A@mail.gmail.com>
24/10/2013 10:09, Jose Gavine Cueto :
> Thank you for the information. Because I would like to copy an rte_mbuf to
> a memory mapped file for an application. Is there some dpdk API for this
> copy operation (linear/nonlinear) or are these left with the application
> developers ?
You can have some tips by looking at rte_pktmbuf_is_contiguous:
http://dpdk.org/doc/api/rte__mbuf_8h.html#a511a116ae4822037d4f1fb561aa4ffcf
and rte_pktmbuf_clone:
http://dpdk.org/doc/api/rte__mbuf_8h.html#a1d26cc982f6363cd7492dd70cc5c287c
--
Thomas
next prev parent reply other threads:[~2013-10-24 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 7:49 Jose Gavine Cueto
2013-10-24 8:03 ` Thomas Monjalon
2013-10-24 8:09 ` Jose Gavine Cueto
2013-10-24 8:32 ` Thomas Monjalon [this message]
2013-10-25 14:04 ` 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=201310241032.14803.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.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).