From: "Neeraj Tandon (netandon)" <netandon@cisco.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Mechanism to increase MBUF allocation
Date: Mon, 15 May 2017 07:14:03 +0000 [thread overview]
Message-ID: <D53EA347.DAED6%netandon@cisco.com> (raw)
Hi,
I have recently started using DPDK. I have based my application on l2fwd application. In my application, I am holding buffers for a period of time and freeing the mbuf in another thread. The default number of MBUF is 8192 . I have two questions regarding this:
1. How to increase number of MBUFS : For this increasing NB_MBUF and calling is not having any effect I.e I loose packet when packets > 8192 are sent in burst. I see following used for creating mbuf pool:
/* create the mbuf pool */
l2fwd_pktmbuf_pool = rte_pktmbuf_pool_create("mbuf_pool", NB_MBUF,
MEMPOOL_CACHE_SIZE, 0, RTE_MBUF_DEFAULT_BUF_SIZE,
rte_socket_id());
If I want to increase MBUF to say 65536 what should I do ?
2. I am receiving packets in RX thread which is running on Core 2 and freeing on a thread which I launched using PHREAD and runs on Core 0 . Any implications for this kind of mechanism
Thanks for the support and keeping forum active.
Regards,
Neenah
next reply other threads:[~2017-05-15 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 7:14 Neeraj Tandon (netandon) [this message]
2017-05-17 3:27 Neeraj Tandon (netandon)
2017-05-18 20:21 ` Neeraj Tandon (netandon)
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=D53EA347.DAED6%netandon@cisco.com \
--to=netandon@cisco.com \
--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).