From: Junjie Chen <junjie.j.chen@intel.com>
To: sergio.gonzalez.monroy@intel.com, john.mcnamara@intel.com,
maryam.tahhan@intel.com, dev@dpdk.org
Cc: Junjie Chen <junjie.j.chen@intel.com>
Subject: [dpdk-dev] [PATCH v3] doc: add a restriction to multi-process support
Date: Wed, 29 Nov 2017 12:17:13 -0500 [thread overview]
Message-ID: <20171129171713.125795-1-junjie.j.chen@intel.com> (raw)
In-Reply-To: <20171128111050.60240-1-junjie.j.chen@intel.com>
This patch add a restriction to multi-process support: secondary
processes should only run alongside primary process with same DPDK
version, so that secondary processes can use the same hugepage mmap
layout as primary process.
Signed-off-by: Junjie Chen <junjie.j.chen@intel.com>
---
v3 changes:
Use 'note' marker to make it clearer.
doc/guides/prog_guide/multi_proc_support.rst | 4 ++++
doc/guides/tools/proc_info.rst | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 9a9dca7fe..4ca3f2c22 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -52,6 +52,10 @@ Standalone DPDK processes are primary processes,
while secondary processes can only run alongside a primary process or
after a primary process has already configured the hugepage shared memory for them.
+.. note::
+
+ Secondary processes should run alongside primary process with same DPDK version.
+
To support these two process types, and other multi-process setups described later,
two additional command-line parameters are available to the EAL:
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index fd17e278c..1b81a7891 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -38,6 +38,10 @@ statistics, resetting port statistics and printing DPDK memory information.
This application extends the original functionality that was supported by
dump_cfg.
+.. note::
+
+ dpdk-procinfo should run alongside primary process with same DPDK version.
+
Running the Application
-----------------------
The application has a number of command line options:
--
2.15.0
next prev parent reply other threads:[~2017-11-29 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 11:10 [dpdk-dev] [PATCH v2] " junjie.j.chen
2017-11-29 17:17 ` Junjie Chen [this message]
2017-12-12 12:41 ` [dpdk-dev] [PATCH v3] " Mcnamara, John
2017-12-12 13:13 ` Chen, Junjie J
2018-02-01 2:17 ` 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=20171129171713.125795-1-junjie.j.chen@intel.com \
--to=junjie.j.chen@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maryam.tahhan@intel.com \
--cc=sergio.gonzalez.monroy@intel.com \
/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).