From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 13F6042D07; Tue, 20 Jun 2023 13:51:15 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F32C740DDA; Tue, 20 Jun 2023 13:51:14 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 50247400D6 for ; Tue, 20 Jun 2023 13:51:13 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 4749E42D08; Tue, 20 Jun 2023 13:51:13 +0200 (CEST) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 21.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: baciumariuscristian@yahoo.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=16872618730.F9C007f.2160258 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --16872618730.F9C007f.2160258 Date: Tue, 20 Jun 2023 13:51:13 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1256 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 end= s up calling mlx5_malloc with the EXTERNAL_HEAP_MIN_SOCKET_ID socket ID, given t= hat no external-memory heap has been created. Instead the rte_extmem_* API is u= sed. 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 memo= ry 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 cac= he 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 regu= lar 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --16872618730.F9C007f.2160258 Date: Tue, 20 Jun 2023 13:51:13 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1256
Summary drivers/common/mlx5: mlx5_malloc() called on invalid socket I= D 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 end=
s up
calling mlx5_malloc with the EXTERNAL_HEAP_MIN_SOCKET_ID socket ID, given t=
hat
no external-memory heap has been created. Instead the rte_extmem_* API is u=
sed.

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 cac=
he
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.
=20=20=20=20=20=20=20=20=20=20
= --16872618730.F9C007f.2160258--