From: 张伟 <zhangwqh@126.com>
To: dev@dpdk.org
Subject: [dpdk-dev] dpdk multi process increase the number of mbufs, throughput gets dropped
Date: Thu, 17 Dec 2015 12:18:36 +0800 (CST) [thread overview]
Message-ID: <44e6e2b3.65ad.151ae293aa7.Coremail.zhangwqh@126.com> (raw)
Hi all,
When running the multi process example, does anybody know that why increasing the number of mbufs, the performance gets dropped.
In multi process example, there are two macros which are related to the number of mbufs
#defineMBUFS_PER_CLIENT1536
|
| #defineMBUFS_PER_PORT1536 |
| |
If increasing these two numbers by 8 times, the performance drops about 10%. Does anybody know why?
| constunsigned num_mbufs = (num_clients * MBUFS_PER_CLIENT) \ |
| | + (ports->num_ports * MBUFS_PER_PORT); |
| pktmbuf_pool = rte_mempool_create(PKTMBUF_POOL_NAME, num_mbufs, |
| | MBUF_SIZE, MBUF_CACHE_SIZE, |
| | sizeof(struct rte_pktmbuf_pool_private), rte_pktmbuf_pool_init, |
| | NULL, rte_pktmbuf_init, NULL, rte_socket_id(), NO_FLAGS ); |
next reply other threads:[~2015-12-17 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 4:18 张伟 [this message]
2015-12-18 12:07 ` Bruce Richardson
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=44e6e2b3.65ad.151ae293aa7.Coremail.zhangwqh@126.com \
--to=zhangwqh@126.com \
--cc=dev@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).