summaryrefslogtreecommitdiff
path: root/doc/guides/prog_guide/multi_proc_support.rst
diff options
context:
space:
mode:
authorKeith Wiles <keith.wiles@intel.com>2017-02-27 11:13:40 -0800
committerThomas Monjalon <thomas.monjalon@6wind.com>2017-03-01 20:39:58 +0100
commit35b09d76f89e7d5a4f38a2926cf6915028ed1e56 (patch)
tree0fb89bd215f4c5549c156701143388107549a2d6 /doc/guides/prog_guide/multi_proc_support.rst
parent048ed1d8284b0e91cd940a3edbd8f79861a6b997 (diff)
downloaddpdk-35b09d76f89e7d5a4f38a2926cf6915028ed1e56.zip
dpdk-35b09d76f89e7d5a4f38a2926cf6915028ed1e56.tar.gz
dpdk-35b09d76f89e7d5a4f38a2926cf6915028ed1e56.tar.xz
doc: use corelist instead of coremask
The coremask option in DPDK is difficult to use and we should be promoting the use of the corelist (-l) option. The patch adjusts the docs to use -l EAL option instead of the -c option. The patch only changes the docs and not the code as the -c option will continue to exist unless it is removed in the future. The -c option should be kept to maintain backward compatibility. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
Diffstat (limited to 'doc/guides/prog_guide/multi_proc_support.rst')
-rw-r--r--doc/guides/prog_guide/multi_proc_support.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 2a996ae..9a9dca7 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -173,7 +173,7 @@ Some of these are documented below:
so it is recommended that it be disabled only when absolutely necessary,
and only when the implications of this change have been understood.
-* All DPDK processes running as a single application and using shared memory must have distinct coremask arguments.
+* All DPDK processes running as a single application and using shared memory must have distinct coremask/corelist arguments.
It is not possible to have a primary and secondary instance, or two secondary instances,
using any of the same logical cores.
Attempting to do so can cause corruption of memory pool caches, among other issues.