From: Anatoly Burakov Date: Thu, 6 Dec 2018 09:30:33 +0000 (+0000) Subject: doc: remove note on memory mode limitation in multi-process X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=41328c404f5023df3dddab5daddad2403c5bb434;p=dpdk.git doc: remove note on memory mode limitation in multi-process Memory mode flags are now shared between primary and secondary processes, so the in documentation about limitations is no longer necessary. Fixes: 64cdfc35aaad ("mem: store memory mode flags in shared config") Cc: stable@dpdk.org Signed-off-by: Anatoly Burakov --- diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst index 5aaac0bd25..929d76dba7 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