From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Han, Dongsu" <dongsu.han@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] app: fix refcnt in mbuf allocation
Date: Mon, 6 May 2013 18:13:50 +0200 [thread overview]
Message-ID: <201305061813.50527.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CAAYH+dWnQ_eP-evFv2ABL8s==Oq1VB0secy1Dj4ZH9BA6ac9wA@mail.gmail.com>
06/05/2013 17:47, Han, Dongsu :
> In addition to this, we should probably clone pkt mbuf using
> rte_pktmbuf_clone()
> and transmit the cloned packet. This will avoid having to copy the mac and
> IP headers.
Yes, it could be faster but it is not always possible because
rte_pktmbuf_clone() is available only if the feature RTE_MBUF_SCATTER_GATHER
is enabled.
--
Thomas
next prev parent reply other threads:[~2013-05-06 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 14:24 [dpdk-dev] suggested patch: testpmd txonly mbuf_alloc does not increment refcnt Han, Dongsu
2013-05-06 12:47 ` [dpdk-dev] [PATCH] app: fix refcnt in mbuf allocation Thomas Monjalon
2013-05-06 13:28 ` Han, Dongsu
2013-05-06 13:56 ` Adrien Mazarguil
2013-05-06 15:47 ` Han, Dongsu
2013-05-06 16:13 ` Thomas Monjalon [this message]
2013-05-06 16:00 ` Thomas Monjalon
2013-05-06 16:13 ` Adrien Mazarguil
2013-05-06 16:33 ` Thomas Monjalon
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=201305061813.50527.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=dongsu.han@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).