Bug 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 | Reporter: | Marius-Cristian Baciu (baciumariuscristian) |
Component: | other | Assignee: | dev |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | rasland |
Priority: | Normal | ||
Version: | 21.11 | ||
Target Milestone: | --- | ||
Hardware: | x86 | ||
OS: | Linux |
Description
Marius-Cristian Baciu
2023-06-20 13:51:13 CEST
This was fixed b this patch: https://git.dpdk.org/dpdk/commit/?h=releases&id=147f6fb42bd7637b37a9180b0774275531c05f9b could you kindly confirm? 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. |