d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: remove note on memory mode limitation in multi-process

Browse Source 
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 <anatoly.burakov@intel.com>
This commit is contained in:
Anatoly Burakov 2018-12-06 09:30:33 +00:00 committed by Thomas Monjalon
parent c3e35a0966
commit 41328c404f
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/guides/prog_guide/env_abstraction_layer.rst
View File

@ -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