DPDK patches and discussions
 help / color / mirror / Atom feed
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 1/2] usage_pktgen.rst: multiple instances: clean up section intro
Date: Thu, 21 Jan 2016 15:46:21 +0000	[thread overview]
Message-ID: <8A27B71D-329B-4AF5-85BD-81B4904E142D@intel.com> (raw)
In-Reply-To: <1453355440-29364-1-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 | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
>diff --git a/docs/source/usage_pktgen.rst b/docs/source/usage_pktgen.rst
>index 20bd314..efe8aa4 100644
>--- a/docs/source/usage_pktgen.rst
>+++ b/docs/source/usage_pktgen.rst
>@@ -103,15 +103,15 @@ Multiple Instances of Pktgen or other application
> =================================================
> 
> One possible solution I use and if you have enough ports available to use.
>-Lets say you need two ports for your application, but you have 4 ports in
>-your system. I physically loop back the cables to have port 0 connect to
>-port 2 and port 1 connected to port 3. Now I can give two ports to my
>-application and two ports to Pktgen.
>-
>-Setup if pktgen and your application you have to startup each one a bit
>-differently to make sure they share the resources like memory and the
>-ports. I will use two Pktgen running on the same machine, which just means
>-you have to setup your application as one of the applications.
>+Let's say you need two ports for your application, but you have 4 ports in
>+your system. I physically loop back the cables to have port 0 connect to port
>+2 and port 1 connected to port 3. Now I can give two ports to my application
>+and two ports to Pktgen.

It appears (if I compared the text correctly) the above only move a few trailing words to the next line, why?
>+
>+If you are running pktgen and your application together, you have to start up
>+each one a bit differently to make sure they share the resources like memory
>+and the ports. I will use two Pktgens running on the same machine, which just
>+means you have imagine your application as one of the applications.

Maybe this is clearer.

If you are running pktgen and your application together, you have to start up
each one a bit differently to make sure they share the resources like memory,
huge page files and ports. I will use two Pktgens running on the same machine,
which just means you have imagine your application as one of the Pktgen instances.


> 
> In my machine I have 8 10G ports and 72 lcores between 2 sockets. Plus I
> have 1024 hugepages per socket for a total of 2048.
>-- 
>2.5.0
>
>


Regards,
Keith





  parent reply	other threads:[~2016-01-21 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  5:50 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
2016-01-21 15:46 ` Wiles, Keith [this message]
2016-01-23  2:46   ` [dpdk-dev] [PKTGEN] [PATCH 1/2] usage_pktgen.rst: multiple instances: clean up section intro 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=8A27B71D-329B-4AF5-85BD-81B4904E142D@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).