[dpdk-dev] [PKTGEN] [PATCH 2/2] usage_pktgen.rst: multiple instances: clarify EAL options needed
keith.wiles at intel.com
Thu Jan 21 16:40:15 CET 2016
On 1/20/16, 11:50 PM, "dev on behalf of Matthew Hall" <dev-bounces at dpdk.org on behalf of mhall at mhcomputing.net> wrote:
>Signed-off-by: Matthew Hall <mhall at mhcomputing.net>
> docs/source/usage_pktgen.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>diff --git a/docs/source/usage_pktgen.rst b/docs/source/usage_pktgen.rst
>index efe8aa4..223d033 100644
>@@ -157,4 +157,19 @@ The -m option then assigns lcores to the ports.
> The information from above is taken from two new files pktgen-master.sh
> and pktgen-slave.sh, have a look at them and adjust as you need.
>+The following DPDK / EAL options must be configured correctly as well:
>+* ``-l lcore_id_list``: non-conflicting list of lcores for each app
If you are going to add -l option then you need to add the -c option too.
>+* ``--master-lcore lcore_id``: non-conflicting master lcore for each app
This option is not required for pktgen or DPDK, which I think we can leave out.
>+* ``-m hugepage_mb / --socket-mem hugepage_mb_list``: non-conflicting amount
>+of hugepage memory for each app, or for each app on each CPU socket
>+* ``--no-shconf``: prevents DPDK from claiming a lockfile that breaks
>+concurrent use of multiple apps
This one is not required, correct? As long as you set the primary processes file-prefix to different prefixes for each one.
>+* ``--file-prefix``: assigns a unique name to the hugepage mmap() files for
> Pktgen can also be configured using the :ref:`commands`.
More information about the dev