[dpdk-users] long initialization of rte_eal_hugepage_init

Tan, Jianfeng jianfeng.tan at intel.com
Wed Sep 6 06:36:01 CEST 2017

> -----Original Message-----
> From: users [mailto:users-bounces at dpdk.org] On Behalf Of ???
> Sent: Wednesday, September 6, 2017 11:25 AM
> To: users at dpdk.org; dev at dpdk.org
> Subject: [dpdk-users] long initialization of rte_eal_hugepage_init
> Hi All,
> I observed that rte_eal_hugepage_init() will take quite long time if there are
> lots of huge pages. Example I have 500 1G huge pages, and it takes about 2
> minutes. That is too long especially for application restart case.
> If the application only needs limited huge page while the host have lots of
> huge pages, the algorithm is not so efficent. Example, we only need 1G
> memory from each socket.
> What is the proposal from DPDK community? Any solution?

You can mount hugetlbfs with "size" option + use "--socket-mem" option in DPDK to restrict the memory to be used. 


> Note I tried version dpdk 16.11.
> Br,
> Wang Zhike

More information about the users mailing list