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 2EC8343CA0; Wed, 13 Mar 2024 16:45:32 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1EE5342DD5; Wed, 13 Mar 2024 16:45:32 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 3743E42E2C for ; Wed, 13 Mar 2024 16:45:30 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 1F5B443CA1; Wed, 13 Mar 2024 16:45:30 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/ethdev Bug 1400] net/ena: Failed to initialize ENA device Date: Wed, 13 Mar 2024 15:45:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 23.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: madhuker.mythri@oracle.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=17103447290.f42e0FeD.3812930 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 --17103447290.f42e0FeD.3812930 Date: Wed, 13 Mar 2024 16:45:29 +0100 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=3D1400 Bug ID: 1400 Summary: net/ena: Failed to initialize ENA device Product: DPDK Version: 23.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: madhuker.mythri@oracle.com Target Milestone: --- Hi, With DPDK-23.11 on AWS cloud with ENA network devices, DPDK initialization failed with 4GB memory for 2 ports. While DPDK rte_eal_init() call on ENA devices, in the ena_com_allocate_customer_metrics_buffer() DPDK memory zone with "ena_p0_mz= 0" is taking lots of memory in GB's just for one zone, why ? As part this call "na_com_allocate_customer_metrics_buffer()" API memory si= ze was passed as '0' (customer_metrics->buffer_len =3D 0) to this "ena_mem_alloc_coherent()" API, which call's --> rte_memzone_reserve_aligne= d() with RTE_MEMZONE_IOVA_CONTIG option.=20 Thus, when memory size is '0' to allocate, this memzone allocated maximum available contiguous memory in GB's. So, for two DPDK ENA ports, this two zones takes around 2GB Or more of mem= ory in DPDK-23.11. For other Mbuf pool's could not allocate memory, as memory exhausted. Why the "customer_metrics->buffer_len =3D 0" size is '0' passing to this ena_mem_alloc_coherent() ? Regards, Madhuker. --=20 You are receiving this mail because: You are the assignee for the bug.= --17103447290.f42e0FeD.3812930 Date: Wed, 13 Mar 2024 16:45:29 +0100 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 1400
Summary net/ena: Failed to initialize ENA device
Product DPDK
Version 23.11
Hardware x86
OS Linux
Status UNCONFIRMED
Severity major
Priority Normal
Component ethdev
Assignee dev@dpdk.org
Reporter madhuker.mythri@oracle.com
Target Milestone --- 

Hi,

With DPDK-23.11 on AWS cloud with ENA network devices, DPDK initialization
failed with 4GB memory for 2 ports.

While DPDK rte_eal_init() call on ENA devices, in the
ena_com_allocate_customer_metrics_buffer() DPDK memory zone with "ena_=
p0_mz0"
is taking lots of memory in GB's just for one zone, why ?

As part this call "na_com_allocate_customer_metrics_buffer()" API=
 memory size
was passed as '0' (customer_metrics->buffer_len =3D 0) to this
"ena_mem_alloc_coherent()" API, which call's --> rte_memzone_r=
eserve_aligned()
with RTE_MEMZONE_IOVA_CONTIG option.=20
Thus, when memory size is '0' to allocate, this memzone allocated maximum
available contiguous memory in GB's.

So, for two DPDK ENA ports, this two zones takes  around 2GB Or more of mem=
ory
in DPDK-23.11. For other Mbuf pool's could not allocate memory, as memory
exhausted.

Why the "customer_metrics->buffer_len =3D 0" size is '0' passi=
ng to this
ena_mem_alloc_coherent() ?

Regards,
Madhuker.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17103447290.f42e0FeD.3812930--