hugepage mapping to memseg failure

[Dmitry Kozlyuk]

Hi Ed,

On Fri, Sep 6, 2024, 16:43 Lombardo, Ed <Ed.Lombardo at netscout.com> wrote:

> The rte_eal_init() arguments are:
>
> ‘app_name, -c0x2, -n4, --socket-mem=2048, --legacy-mem, --no-telemetry’
>
>
>
> Could it be that the hugpages are not contiguous and reboot clears this
> issue, not able to confirm.
>
Yes, this is likely the root cause. Since you're building DPDK yourself,
you can print cur->physaddr around line 900 (see the link below). In legacy
mode, DPDK leaves "holes" (unused elements) in memory segment lists between
pages that are not physically contiguous. Because in your case the segment
list has only two elements, there is no room for two segments for two
hugepages plus a hole segment between them.
http://git.dpdk.org/dpdk/tree/lib/eal/linux/eal_memory.c#n832

Your options then are:
- not using legacy memory mode;
- increasing *_MAX_MEM_MB_* constants to 3072 (will also increase VIRT).

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/users/attachments/20240907/6a2f63bf/attachment.htm>