[dpdk-dev] App crash when using no-huge option

[damu <2103458176@qq.com>]

Hi,

Today I tried no-huge option with app/test, the test app crashed.
It seems that memory can not be allocated. 
I think it could be this change causing the panic. Can someone check it?

commit 2d65283c259616a5643599ce32d7a62d174ec49e
Author: Cyril Chemparathy <cchemparathy@ezchip.com>
Date:   Thu Jul 9 16:25:14 2015 +0800

    mem: refactor memzone reserve functions


 sudo ./app/test -c 3 -n 2 --no-huge

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up memory...
RING: Cannot reserve memory for tailq
EAL: rte_eal_common_log_init(): cannot create log_history mempool
PANIC in rte_eal_init():
Cannot init logs
6: [./app/test() [0x42c1f3]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1d65354ec5]]
4: [./app/test(main+0x11) [0x42a161]]
3: [./app/test(rte_eal_init+0xeae) [0x5106fe]]
2: [./app/test(__rte_panic+0xc9) [0x425c6e]]
1: [./app/test(rte_dump_stack+0x18) [0x516e28]]