From: MOD <sdk.register@gmail.com>
To: users@dpdk.org
Subject: Mempool bigger than 1 page causes segmentation fault
Date: Wed, 27 Jul 2022 14:59:24 +0300 [thread overview]
Message-ID: <CA+Md9nzuk7V-vJv=hH8QBbtZU9X=W4VyhTUYLVyiVUV5hY5TNQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hi All,
My team and I have encountered a problem where allocation of a mempool
larger than 1GB (== 1 Hugepage) fails.
We are in a multi-process environment, and the `rte_mempool_create`
happens in the secondary process.
Sometimes the allocation succeeds but after some successes (for me
specifically, two) the following occurs:
the secondary process segfaults on `malloc_elem_can_hold`, inside a stack
starting from `rte_mempool_create`.
Restarting the secondary process does not work as it is stuck on `EAL:
Probing VFIO support`, and restarting
the main process is the only option.
Has anyone had this problem, or knows any possible solution?
Thanks!
[-- Attachment #2: Type: text/html, Size: 818 bytes --]
next reply other threads:[~2022-07-27 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 11:59 MOD [this message]
2022-07-27 12:30 ` Dmitry Kozlyuk
[not found] ` <CA+Md9nye7c6X9=9bFc3kp+zOQEASM6-PeqW7i-G=xHRkG5PG4A@mail.gmail.com>
2022-07-28 13:10 ` Dmitry Kozlyuk
2022-07-31 11:32 ` MOD
2022-09-07 11:00 ` MOD
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='CA+Md9nzuk7V-vJv=hH8QBbtZU9X=W4VyhTUYLVyiVUV5hY5TNQ@mail.gmail.com' \
--to=sdk.register@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).