From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 50] Secondary process launch is unreliable
Date: Tue, 22 May 2018 16:15:47 +0000 [thread overview]
Message-ID: <bug-50-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=50
Bug ID: 50
Summary: Secondary process launch is unreliable
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: anatoly.burakov@intel.com
Target Milestone: ---
Secondary process initialization was known to be unreliable before, with
numerous workarounds already being available and documented. However, DPDK
version 18.05 has introduced memory subsystem rework, which has made situation
worse due to much more memory being pre-reserved at initialization.
In addition, following investigation, it was revealed that DPDK secondary
processes ran with fork()/execv() method from within another DPDK application
(such as is the case with some DPDK unit tests) carry an additional risk of
initialization failures due to how pthread library appears to be working under
these conditions. Specifically, two IPC threads created by EAL will take up a
lot of address space (more than 10x of the usual amount), thereby interfering
with secondary process mappings and causing initialization failure. In this
case, disabling ASLR may actually make the situation worse, as
non-deterministic but sometimes lucky memory layout will be replaced by
deterministically wrong address mappings.
Things to try when affected by this issue:
* Using --base-virtaddr to relocate DPDK memory segments at initialization
* Not running DPDK applications using fork()/execv() method
* Enabling or disabling ASLR
* Recompiling the binary with different configuration
* Reducing the amount of preallocated memory (adjusting config options
CONFIG_RTE_MAX_MEM_MB_PER_TYPE and/or RTE_MAX_MEM_MB_PER_LIST)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-05-22 16:15 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-50-3@http.dpdk.org/tracker/ \
--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).