Hi All,
I saw this explanation for using -no-hugepage option.
http://mails.dpdk.org/archives/dev/2016-November/050109.html
>* When using --no-huge, the dpdk libraries (including mempool) allocate
*>* its memory in standard memory. Just keep in mind the physical addresses
*>* will be wrong, so
Hi all,
My target software stack does not support hugetlbfs, but it supports
huge-paged mmaps. I'm trying to port dpdk huge-page allocate logic to use
mmap based allocations. Hence the below question. I use dpdk 16.11.1 (
slightly old i know :) )
I see that, there is
1. malloc based allocation