From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 872] rte_malloc() faild in secondary process with dynamic memory mode
Date: Mon, 01 Nov 2021 06:02:14 +0000 [thread overview]
Message-ID: <bug-872-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=872
Bug ID: 872
Summary: rte_malloc() faild in secondary process with dynamic
memory mode
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: li_hong.bi@nokia-sbell.com
Target Milestone: ---
We have one primary dpdk process and 4 secondary processes, and 4 secondary
processes will call rte_malloc() to allocate some memory and call rte_free() to
release memory after process something.
1. if dpdk memory mode is dynamic, rte_malloc() failed will occur and 'EAL:
Request timed out' log was printed out.
2. if dpdk memory mode is legacy, it is normal without any issue.
Note: from current investigation, when this issue occurred, the new hugepage
block was reserved and released from/to system.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-11-01 6:02 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-872-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).