On 07-Aug-19 2:28 PM, Hemant Agrawal wrote:
HI Thomas,
DPDK currently is supporting maximum 3 hugepage, sizes whereas
system can support more than this e.g.
64K, 2M, 32M and 1G.
You can mention ARM platform here, and that this issue starts with
kernel 5.2 (and I would try to mention this in the title as well).
This is better than an annotation that will be lost.
Having these four hugepage sizes available to use by DPDK, which is
valid in case of '--in-memory' EAL option or using 4 separate mount
points for each hugepage size;
hugepage_info_init() API reports an error.
Can you describe what is the impact from a user point of view rather
than mentioning this internal function?
Yes please, we need to understand how much it is critical.
Should we Cc sta...@dpdk.org for backport?
Should it be merged at the last minute in 19.08?
VPP usages in-memory option. So, VPP on ARM with kernel 5.2 wont' work without
this patch.
Off-topic, but it's nice to see real-world usage for this option!
--
Thanks,
Anatoly
