From: Andriy Berestovskyy <aber@semihalf.com>
To: "forsakening@sina.cn" <forsakening@sina.cn>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Is anybody test rte_mbuf_free performance?
Date: Mon, 22 Aug 2016 19:40:35 +0200 [thread overview]
Message-ID: <CAOysbxo00erRR_pd2GoTyd6ZkN9UkceDBd+PpGKOqmcybHPa4A@mail.gmail.com> (raw)
In-Reply-To: <201608222037241031642@sina.cn>
Hi,
Here are few suggestions for you:
1. Try to increase mempool cache.
2. Try to split the load across few mempools.
3. Try to free in bulks as many PMDs do.
Regards,
Andriy
On Mon, Aug 22, 2016 at 2:37 PM, forsakening@sina.cn
<forsakening@sina.cn> wrote:
> Hi Everyone：
> I found rte_pktmbuf_free not performe so well when using greater than 12 parallel caller。
> Is anyone meet the same problem ？Thanks for giving a direction.
>
>
>
> forsakening@sina.cn
--
Andriy Berestovskyy
prev parent reply other threads:[~2016-08-22 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:37 forsakening
2016-08-22 17:40 ` Andriy Berestovskyy [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=CAOysbxo00erRR_pd2GoTyd6ZkN9UkceDBd+PpGKOqmcybHPa4A@mail.gmail.com \
--to=aber@semihalf.com \
--cc=forsakening@sina.cn \
--cc=users@dpdk.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 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).