From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
ferruh.yigit@intel.com, thomas@monjalon.net
Subject: [dpdk-dev] [PATCH] doc: document known issues for multiprocess
Date: Mon, 28 May 2018 12:28:53 +0100 [thread overview]
Message-ID: <3f438d1d23d2d2792f2fe92d587097ec958ffe4e.1527506897.git.anatoly.burakov@intel.com> (raw)
Also, reference Bugzilla entry for keeping most current information in
one place.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
doc/guides/rel_notes/release_18_05.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index e8d74f5..032d303 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -568,6 +568,15 @@ Known Issues
dpdk-pdump example and any other applications using librte_pdump, cannot work
with older version DPDK primary applications.
+* **Secondary process launch is not reliable.**
+
+ Recent memory hotplug patches have made multiprocess startup less reliable
+ than it was in the past. A number of workarounds are known to work depending
+ on the circumstances, all of which are detailed in the Bugzilla entry
+ referenced below.
+
+ Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=50
+
Shared Library Versions
-----------------------
--
2.7.4
next reply other threads:[~2018-05-28 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 11:28 Anatoly Burakov [this message]
2018-05-29 15:43 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2018-05-29 16:49 ` Mcnamara, John
2018-05-30 12:14 ` Thomas Monjalon
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=3f438d1d23d2d2792f2fe92d587097ec958ffe4e.1527506897.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).