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: Tue, 20 Jun 2023 11:51:13 +0000 [thread overview]
Message-ID: <bug-1256-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1256
Bug ID: 1256
Summary: drivers/common/mlx5: mlx5_malloc() called on invalid
socket ID when global MR cache is full and
rte_extmem_* API is used
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: baciumariuscristian@yahoo.com
Target Milestone: ---
Overview:
Attempt to allocate a new mlx5 MR entry when global Btree cache is full ends up
calling mlx5_malloc with the EXTERNAL_HEAP_MIN_SOCKET_ID socket ID, given that
no external-memory heap has been created. Instead the rte_extmem_* API is used.
Steps to reproduce:
- start a primary DPDK process, on a NIC compatible with mlx5_core driver;
- use rte_extmem_register() to register >512 pages of 4KB;
- use rte_dev_dma_map() to dma-map each page;
- rte_eth_tx_burst() an mbuf with an external buffer from the last page of the
registered memory (or a page above index 512). (a virtual address that will not
be found in the global Btree cache);
Actual results:
mlx5_malloc in mlx5_mr_create_primary() fails with "Unable to allocate memory
for a new MR". From this point forward, packets never reach the other end.
Expected results:
MR entries should be successfully retrieved from backup or created when cache
becomes full; calling mlx5_malloc() on external heap socket should not be
possible when rte_extmem_* API is used. As it is stated in the DPDK
documentation[1], "Memory added this way will not be available for any regular
DPDK allocators".
Build Date & Hardware:
20 Jun 2023 on Debian GNU/Linux 4.18.0
[1]: https://doc.dpdk.org/guides-21.11/prog_guide/env_abstraction_layer.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4007 bytes --]
next reply other threads:[~2023-06-20 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:51 bugzilla [this message]
2023-07-06 8:29 ` [Bug 1256] drivers/common/mlx5: mlx5_malloc() called on invalid socket ID when global MR cache is full and rte_extmem_* API is used bugzilla
2023-07-06 9:06 ` bugzilla
2025-11-05 9:22 ` [DPDK/other Bug " bugzilla
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.