DPDK usage discussions
 help / color / mirror / Atom feed
From: Anna Tauzzi <admin@argonnetech.net>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Secondary process stuck in rte_eal_memory_init
Date: Wed, 24 Aug 2022 11:18:38 +0200	[thread overview]
Message-ID: <CAK_0FMRMM7pnp9OuVMbcoL+h556MmyGwMkqVXH7r86F5QyU0MQ@mail.gmail.com> (raw)
In-Reply-To: <CAO8pfF=V+tuEHFswean0Z6avWkd3KXSDBHVrBiuQWsadBeFerw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Already tried the first suggestion with no luck, the secondary always gets
stuck:

#0  0x00007fc6d3eb05ab in flock () at ../sysdeps/unix/syscall-template.S:78
#1  0x00007fc6d3ba1343 in sync_walk () from /usr/local/lib/librte_eal.so.22
#2  0x00007fc6d3b8402b in rte_memseg_list_walk_thread_unsafe () from
/usr/local/lib/librte_eal.so.22
#3  0x00007fc6d3ba18bf in eal_memalloc_sync_with_primary () from
/usr/local/lib/librte_eal.so.22
#4  0x00007fc6d3ba24b5 in rte_eal_hugepage_attach () from
/usr/local/lib/librte_eal.so.22
#5  0x00007fc6d3b848f1 in rte_eal_memory_init () from
/usr/local/lib/librte_eal.so.22
#6  0x00007fc6d3b782aa in rte_eal_init.cold () from
/usr/local/lib/librte_eal.so.22

For the second info:
if I prevent  the primary to allocate on the NUMA where  secondary is
running, then, the secondary doesn't get stuck.




Il giorno mer 24 ago 2022 alle ore 11:14 Antonio Di Bacco <
a.dibacco.ks@gmail.com> ha scritto:

> Can you try launching the secondary with some delay in order not to
> overlap with memory allocations done in the primary?
> Is your primary allocating memory on NUMA 0 where the secondary is running?
>
> On Tue, Aug 23, 2022 at 4:54 PM Anna Tauzzi <admin@argonnetech.net> wrote:
> >
> > 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: 2496 bytes --]

  reply	other threads:[~2022-08-24  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 14:54 Anna Tauzzi
2022-08-24  9:14 ` Antonio Di Bacco
2022-08-24  9:18   ` Anna Tauzzi [this message]
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_0FMRMM7pnp9OuVMbcoL+h556MmyGwMkqVXH7r86F5QyU0MQ@mail.gmail.com \
    --to=admin@argonnetech.net \
    --cc=a.dibacco.ks@gmail.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).