From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: users <users@dpdk.org>
Subject: Re: hugepage mapping to memseg failure
Date: Sat, 7 Sep 2024 23:35:58 +0300 [thread overview]
Message-ID: <CAEYuUWAnT==wB1waayji+KTQWZjjwAK61mMwcoNOjnD_q2uekQ@mail.gmail.com> (raw)
In-Reply-To: <CH3PR01MB8470B651CE8BDCB4F0D32F7D8F9E2@CH3PR01MB8470.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi Ed,
On Fri, Sep 6, 2024, 16:43 Lombardo, Ed <Ed.Lombardo@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).
>
[-- Attachment #2: Type: text/html, Size: 2052 bytes --]
next prev parent reply other threads:[~2024-09-07 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 22:23 hugepage allocation mapping failure Lombardo, Ed
2024-09-06 13:42 ` hugepage mapping to memseg failure Lombardo, Ed
2024-09-07 20:35 ` Dmitry Kozlyuk [this message]
2024-09-10 20:42 ` Lombardo, Ed
2024-09-10 22:36 ` Dmitry Kozlyuk
2024-09-11 4:26 ` Lombardo, Ed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEYuUWAnT==wB1waayji+KTQWZjjwAK61mMwcoNOjnD_q2uekQ@mail.gmail.com' \
--to=dmitry.kozliuk@gmail.com \
--cc=Ed.Lombardo@netscout.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).