From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1256] drivers/common/mlx5: mlx5_malloc() called on invalid socket ID when global MR cache is full and rte_extmem_* API is used
Date: Thu, 06 Jul 2023 09:06:49 +0000 [thread overview]
Message-ID: <bug-1256-3-dAdIRCvdcn@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1256-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1256
Marius-Cristian Baciu (baciumariuscristian@yahoo.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |UNCONFIRMED
--- Comment #3 from Marius-Cristian Baciu (baciumariuscristian@yahoo.com) ---
Hi,
Unfortunately that patch only targets a memory socket issue with the ASO
mechanism. However, in my setup ASO is never an issue - I actually do not
believe it is enabled.
To give a little more insight, the problem I am describing manifests on the
data path:
- rte_eth_tx_burst();
- mlx5_tx_burst_*() is called;
- at some later point, in mr_lookup_caches(), mr_btree_lookup() returns
UINT32_MAX because all 256 entries in the cache have been occupied and last
memory registration did not catch an empty slot;
- when mr_lookup_caches() fails, mlx5_mr_create() -> mlx5_mr_create_primary()
is called;
- mlx5_malloc() at line 723 fails because it is called with an inappropriate
socket ID (the socket ID of the memseg list associated with an external buffer
(prior with rte_extmem_register()), EXTERNAL_HEAP_MIN_SOCKET_ID, which does not
actually have a valid heap associated, from which memory could be allocated.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3679 bytes --]
prev parent reply other threads:[~2023-07-06 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:51 bugzilla
2023-07-06 8:29 ` bugzilla
2023-07-06 9:06 ` bugzilla [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=bug-1256-3-dAdIRCvdcn@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).