From: Anna Tauzzi <admin@argonnetech.net>
To: users@dpdk.org
Subject: Secondary process stuck in rte_eal_memory_init
Date: Tue, 23 Aug 2022 16:54:09 +0200 [thread overview]
Message-ID: <CAK_0FMSACCHrL9CXwFkJ3e_Dg6Akk0PuUTSjndiDsbS8F-ey+A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
I have a primary process that spawns a secondary process.Primary is on NUMA
1 while secondary on NUMA 0.
The secondary process starts up but when calling rte_eal_init it gets stuck
with this backtrace:
flock()
sync_walk()
rte_memseg_list_walk_thread_unsafe()
eal_memalloc_sync_with_primary()
rte_eal_hugepage_attach()
rte_eal_memory_init()
rte_eal_init.cold()
While starting the secondary, it is possible that the primary is allocating
memory on different NUMAs. I'm saying this because if in the primary I
replace the dpdk memory allocation function (rte_zalloc...) with a plain
memalign I don't get this problem.
[-- Attachment #2: Type: text/html, Size: 811 bytes --]
next reply other threads:[~2022-08-23 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 14:54 Anna Tauzzi [this message]
2022-08-24 9:14 ` Antonio Di Bacco
2022-08-24 9:18 ` Anna Tauzzi
2022-08-24 10:11 ` Anna Tauzzi
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=CAK_0FMSACCHrL9CXwFkJ3e_Dg6Akk0PuUTSjndiDsbS8F-ey+A@mail.gmail.com \
--to=admin@argonnetech.net \
--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).