[dpdk-dev] [PATCH] doc: remove note on limitations for memory mode in secondary

Anatoly Burakov anatoly.burakov at intel.com
Thu Dec 6 10:30:33 CET 2018

Memory mode flags are now shared between primary and secondary
processes, so the in documentation about limitations is no longer

Fixes: 64cdfc35aaad ("mem: store memory mode flags in shared config")
Cc: stable at dpdk.org

Signed-off-by: Anatoly Burakov <anatoly.burakov at intel.com>
 doc/guides/prog_guide/env_abstraction_layer.rst | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index 8b5d050c7..426acfc28 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -147,15 +147,6 @@ A default validator callback is provided by EAL, which can be enabled with a
 ``--socket-limit`` command-line option, for a simple way to limit maximum amount
 of memory that can be used by DPDK application.
-.. note::
-    In multiprocess scenario, all related processes (i.e. primary process, and
-    secondary processes running with the same prefix) must be in the same memory
-    modes. That is, if primary process is run in dynamic memory mode, all of its
-    secondary processes must be run in the same mode. The same is applicable to
-    ``--single-file-segments`` command-line option - both primary and secondary
-    processes must shared this mode.
 + Legacy memory mode
 This mode is enabled by specifying ``--legacy-mem`` command-line switch to the

More information about the dev mailing list