From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Wajeeha Javed <wajeeha.javed123@gmail.com>, <users@dpdk.org>
Subject: Re: [dpdk-users] Increasing the NB_MBUFs of PktMbuf MemPool
Date: Fri, 12 Oct 2018 11:56:48 +0300 [thread overview]
Message-ID: <b71716b2-2888-6828-3cfc-568c684c3181@solarflare.com> (raw)
In-Reply-To: <CAAQUUHUbowa5EnTiOhsaimAXNJXxjxKgPY1GAsqR+EUtoGL_2w@mail.gmail.com>
Hi,
On 10/12/18 7:48 AM, Wajeeha Javed wrote:
> Hi,
>
> I am in the process of developing DPDK based Application where I would
> like to delay the packets for about 2 secs. There are two ports connected
> to DPDK App and sending traffic of 64 bytes size packets at a line rate of
> 10GB/s. Within 2 secs, I will have 28 Million packets for each of the port
> in delay application. The maximum RX Descriptor size is 16384. I am unable
> to increase the number of Rx descriptors more than 16384 value. Is it
> possible to increase the number of Rx descriptors to a large value. e.g.
> 65536. Therefore I copied the mbufs using the pktmbuf copy code(shown
> below) and free the packet received. Now the issue is that I can not copy
> more than 5 million packets because the nb_mbufs of the mempool can't be
> more than 5 Million (#define NB_MBUF 5000000). If I increase the NB_MBUF
> macro from more than 5 Million, the error is returned unable to init mbuf
> pool. Is there a possible way to increase the mempool size?
I've failed to find explicit limitations from the first glance.
NB_MBUF define is typically internal to examples/apps.
The question I'd like to double-check if the host has enought
RAM and hugepages allocated? 5 million mbufs already require about
10G.
Andrew.
next prev parent reply other threads:[~2018-10-12 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 4:48 Wajeeha Javed
2018-10-12 8:56 ` Andrew Rybchenko [this message]
2018-10-12 11:35 ` Wiles, Keith
2018-10-12 11:40 ` Wiles, Keith
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=b71716b2-2888-6828-3cfc-568c684c3181@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=users@dpdk.org \
--cc=wajeeha.javed123@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).