From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: MOD <sdk.register@gmail.com>
Cc: users@dpdk.org
Subject: Re: Mempool bigger than 1 page causes segmentation fault
Date: Thu, 28 Jul 2022 16:10:20 +0300 [thread overview]
Message-ID: <20220728161020.179f1fc7@sovereign> (raw)
In-Reply-To: <CA+Md9nye7c6X9=9bFc3kp+zOQEASM6-PeqW7i-G=xHRkG5PG4A@mail.gmail.com>
2022-07-28 15:05 (UTC+0300), MOD:
> Hi, Thanks for the response!
> the DPDK version is 20.11.4
>
> the stack trace is:
> malloc_elem_can_hold() // librte_eal.so.21
> find_suitable_element() // librte_eal.so.21
> malloc_heap_alloc() // librte_eal.so.21
> rte_memzone_reserve_thread_safe() // librte_eal.so.21
> rte_mempool_populate_default() // librte_mempool.so.21
> rte_mempool_create() // librte_mempool.so.21
Is this all the info---no arguments, no lines?
You're using a debug build of DPDK, right?
> RTE_MALLOC_DEBUG doesn't seem to change anything,
> but I noticed that I have been wrong about the allocation succeeding
> (not because of RTE_MALLOC_DEBUG)
>
> the error happens right on the first attempt.
Did you try running with ASAN (meson -Db_sanitize=address)?
Can you provide a short code to reproduce
or does it happen only in a larger program?
Please keep Cc: users@dpdk.org so that more people can join if they want.
next prev parent reply other threads:[~2022-07-28 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 11:59 MOD
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 [this message]
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=20220728161020.179f1fc7@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=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).