[dpdk-dev] [PATCH] eal: change max hugepage sizes to 4

[Thomas Monjalon]

07/08/2019 15:28, Hemant Agrawal:
> 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 stable at 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. 

Do you want to send a v2 with a better explanation?

I would suggest to restrict the change to Arm only with an ifdef,
in order to limit the risk for this release.
We can think about a dynamic hugepage scan in the next release.