DPDK currently is supporting maximum 3 hugepage, sizes whereas system can support more than this e.g. 64K, 2M, 32M and 1G.
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. This change increases the maximum supported mount points to 4. Signed-off-by: Gagandeep Singh <g.si...@nxp.com> Signed-off-by: Nipun Gupta <nipun.gu...@nxp.com> --- On ARM platform when the translation granule is 4KB, there are 4 hugepage sizes supported. On kernel 5.2, we can see below directories in /sys/kernel/mm/hugepages: hugepages-1048576kB hugepages-2048kB hugepages-32768kB hugepages-64kB lib/librte_eal/common/eal_internal_cfg.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/librte_eal/common/eal_internal_cfg.h b/lib/librte_eal/common/eal_internal_cfg.h index edff09d07..abb7ec913 100644 --- a/lib/librte_eal/common/eal_internal_cfg.h +++ b/lib/librte_eal/common/eal_internal_cfg.h @@ -15,7 +15,7 @@ #include "eal_thread.h" -#define MAX_HUGEPAGE_SIZES 3 /**< support up to 3 page sizes */ +#define MAX_HUGEPAGE_SIZES 4 /**< support up to 4 page sizes */ /* * internal configuration structure for the number, size and -- 2.17.1
