[dpdk-dev] Memory requirement calculation to create mempools with external memory

Hi, My goal is to create mbuf pools using external memory with rte_malloc_heap_*(). The initial implementation goes like this: - Create an empty heap rte_malloc_heap_create() - Calculate memory required - Provision and add the calculated single memory chunk to the heap rte_malloc_heap_memory_ad

Re: [dpdk-dev] Inconsistent behavior of mempool with regards to hugepage allocation

Hi Olivier, > On 27 Dec 2019, at 4:11 PM, Olivier Matz wrote: > > On Thu, Dec 26, 2019 at 04:45:24PM +0100, Olivier Matz wrote: >> Hi Bao-Long, >> >> On Mon, Dec 23, 2019 at 07:09:29PM +0800, Bao-Long Tran wrote: >>> Hi, >>> >>> I'm n

[dpdk-dev] Inconsistent behavior of mempool with regards to hugepage allocation

Hi, I'm not sure if this is a bug, but I've seen an inconsistency in the behavior of DPDK with regards to hugepage allocation for rte_mempool. Basically, for the same mempool size, the number of hugepages allocated changes from run to run. Here's how I reproduce with DPDK 19.11. IOVA=pa (default

[dpdk-dev] rte_eal_init() behavior

Hi, In most of the examples, the argc and argv from main are passed directly to rte_eal_init(). This has the implication that argv[0] is the program name. When a user crafts his own argv, he must submit a placeholder at argv[0] as well, or else the EAL parameters won't be parsed correctly. Below