From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
Cc: dev@dpdk.org
Subject: Re: rte_mempool_create/alloc_seg crash
Date: Mon, 13 May 2024 19:08:42 +0300 [thread overview]
Message-ID: <20240513190842.054fa6c2@sovereign> (raw)
In-Reply-To: <CAAFk=6C_4L7jYeqpUEzgi+A9MW+1Z7ydPfWTCj40ANYR+CetSQ@mail.gmail.com>
2024-05-13 18:37 (UTC+0300), Oleksandr Nahnybida:
[snip]
> I think ignore_msk |= last_msk; should be replaced by cur_msk &=
> last_msk; I tried this and dpdk doesn't crash anymore and seems to
> work fine, but I'd like someone else familiar with this code to take a look
> at this.
I confirm this bug exists and the proposed fix works. We have encountered it
too and the same fix has been working in the field for some time by now.
To clarify the bug condition, our conclusion is that it happens when:
- the size of memseg array is not a multiple of 64
- the last array element is free (for rte_fbarray_find_next_n_free)
- there aren't consequent N free elements in the array
prev parent reply other threads:[~2024-05-13 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 15:37 rte_mempool_create/alloc_seg crash Oleksandr Nahnybida
2024-05-13 16:08 ` Dmitry Kozlyuk [this message]
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=20240513190842.054fa6c2@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=oleksandrn@interfacemasters.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).