DPDK usage discussions
 help / color / mirror / Atom feed
From: MOD <sdk.register@gmail.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: users@dpdk.org
Subject: Re: Mempool bigger than 1 page causes segmentation fault
Date: Sun, 31 Jul 2022 14:32:47 +0300	[thread overview]
Message-ID: <CA+Md9nzPS6fmp0=R1yb6KpCLzd+c1J_rG=1JW7awrmOHowmWQA@mail.gmail.com> (raw)
In-Reply-To: <20220728161020.179f1fc7@sovereign>

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

Hi,
The issue is probably not with my code but with the compilation on DPDK,
because I got it to repeat on a separated program,
where I setup an EAL with the flags `-l 1 --no-pci`
(just rte_eal_init and rte_mempool_create)

this seems to be a memseg_list issue
When running the program  above, and requesting large amounts of memory
(200M elements of 8 bytes each)
I don't crash, but get `couldnt find suitable memseg_list` error
This also happens when trying to allocate from  the main process

This error is probably related to these parameters from rte_config.h:
/* EAL defines */
#define RTE_MAX_HEAPS 32
#define RTE_MAX_MEMSEG_LISTS 128
#define RTE_MAX_MEMSEG_PER_LIST 8192
#define RTE_MAX_MEM_MB_PER_LIST 32768
#define RTE_MAX_MEMSEG_PER_TYPE 32768
#define RTE_MAX_MEM_MB_PER_TYPE 65536
#define RTE_MAX_MEMZONE 2560
#define RTE_MAX_TAILQ 32


I could not find a good documentation on how to calculate the proper values
for these parameters


On Thu, Jul 28, 2022 at 4:10 PM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
wrote:

> 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.
>

[-- Attachment #2: Type: text/html, Size: 11897 bytes --]

  reply	other threads:[~2022-07-31 11:33 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
2022-07-31 11:32       ` MOD [this message]
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+Md9nzPS6fmp0=R1yb6KpCLzd+c1J_rG=1JW7awrmOHowmWQA@mail.gmail.com' \
    --to=sdk.register@gmail.com \
    --cc=dmitry.kozliuk@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).