From: "Wiles, Keith" <keith.wiles@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] [PATCH 2/2] usage_pktgen.rst: multiple instances: clarify EAL options needed
Date: Thu, 21 Jan 2016 15:40:15 +0000 [thread overview]
Message-ID: <2143F83B-CDAE-405B-87B5-437437C25BCE@intel.com> (raw)
In-Reply-To: <1453355440-29364-2-git-send-email-mhall@mhcomputing.net>
On 1/20/16, 11:50 PM, "dev on behalf of Matthew Hall" <dev-bounces@dpdk.org on behalf of mhall@mhcomputing.net> wrote:
>Signed-off-by: Matthew Hall <mhall@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
>--- a/docs/source/usage_pktgen.rst
>+++ b/docs/source/usage_pktgen.rst
>@@ -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
>+each app
>+
> Pktgen can also be configured using the :ref:`commands`.
>--
>2.5.0
>
>
Regards,
Keith
next prev parent reply other threads:[~2016-01-21 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:50 [dpdk-dev] [PKTGEN] [PATCH 1/2] usage_pktgen.rst: multiple instances: clean up section intro Matthew Hall
2016-01-21 5:50 ` [dpdk-dev] [PKTGEN] [PATCH 2/2] usage_pktgen.rst: multiple instances: clarify EAL options needed Matthew Hall
2016-01-21 15:40 ` Wiles, Keith [this message]
2016-01-21 15:46 ` [dpdk-dev] [PKTGEN] [PATCH 1/2] usage_pktgen.rst: multiple instances: clean up section intro Wiles, Keith
2016-01-23 2:46 ` Matthew Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2143F83B-CDAE-405B-87B5-437437C25BCE@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).