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 [thread overview]
Message-ID: <bug-1400-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1400
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 = 0) to this
"ena_mem_alloc_coherent()" API, which call's --> rte_memzone_reserve_aligned()
with RTE_MEMZONE_IOVA_CONTIG option.
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 memory
in DPDK-23.11. For other Mbuf pool's could not allocate memory, as memory
exhausted.
Why the "customer_metrics->buffer_len = 0" size is '0' passing to this
ena_mem_alloc_coherent() ?
Regards,
Madhuker.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3443 bytes --]
reply other threads:[~2024-03-13 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1400-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 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).