From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id B84061B20C for ; Fri, 12 Oct 2018 10:57:34 +0200 (CEST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us3.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id B64166C0075; Fri, 12 Oct 2018 08:57:33 +0000 (UTC) Received: from [192.168.38.17] (91.220.146.112) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 12 Oct 2018 09:57:29 +0100 To: Wajeeha Javed , References: From: Andrew Rybchenko Message-ID: Date: Fri, 12 Oct 2018 11:56:48 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB X-Originating-IP: [91.220.146.112] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24150.003 X-TM-AS-Result: No-7.005500-8.000000-10 X-TMASE-MatchedRID: +f/wAVSGjugOwH4pD14DsPHkpkyUphL9fkuZtv/FS5phe8qthb7NtzC0 pJIQUiJOBSMYw6mnEcO/GjIHLzn7Bp9fRAHWYtIPO9+ygK4Bw/6l9VzHf0qr7vWAXs8IQX1u9nq mLTa9xTLL71REO+8WBgGIiXEQTvX7IDV2A6Nq0YayBjDX4sGuTX6AgKJtUpGrc/T3GfQUvxmk1E CsA9Rjseg7eTQpsrlltDSLcdQPV8w25XOhnouJ5SI9MxSOQ6CSXgqwd9ijktCjC1E/zCEIrwrxO vLvFPZPEeHflL4ZdKr9Vaa04yzrEU9dh3PRYVY1AP2Bflpd3h/HbZsG8T5ZjjssXelfet1UuPFr kRUFXWri8zVgXoAltkWL4rBlm20vIhDmZnlKoc8viEIyyOmsmhPqGErhoUCDN0R7KF6B1W9f3hx UMPNB/tqyF8xHgfJYAAX8dwSi2ZIw1yzhhmPL9FHX6YvaUfSeku+Rybz1q2E2RRIMOrvjaQ== X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--7.005500-8.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24150.003 X-MDID: 1539334654-rRxo9uCeHPLa Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Increasing the NB_MBUFs of PktMbuf MemPool X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 08:57:34 -0000 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.