DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Marko Niinimaki <manzikki@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Pktgen performance tricks
Date: Thu, 23 Jun 2016 14:17:18 +0000	[thread overview]
Message-ID: <231BE07A-F689-41BA-8852-D8E240DAAB59@intel.com> (raw)
In-Reply-To: <CAMfE_jet1r-y-JvCw0JZQT9eaEoFZrXeKKWmmXppm=AxxJci7A@mail.gmail.com>


On 6/23/16, 12:33 PM, "users on behalf of Marko Niinimaki" <users-bounces@dpdk.org on behalf of manzikki@gmail.com> wrote:

>Hi, apologies for such a simple question:
>I'm able to send about 4M custom packets by Pktgen using the following
>parameters:
>pktgen -c 0x3 -n 4 --  -m "1.0"
>Hoping to speed up, I added some more cores with
>pktgen -c 0x7 -n 4 --  -m "1.0, 2.1"
>but this does not really improve the performance. I've been tinkering a
>bit, but no great breaktrough. What would be the best approach/parameters?
>I'm only interested in TX this time.

Can you tell me more about the system like how many cores maybe run the cpu_layout.py script in the tools directory?
Also the type of NIC being used 1G, 10G or 40G?

Normally the best performance is to split the TX and RX of a single port on to two different physical cores. If you have hyper-threading enabled then make sure the two lcores being used are on the same socket, but two different cores.

Pktgen is able to send close to 10GB 64 byte frames on a single XEON core.

Try pktgen –l 1-3 –n 4 -- -m “[2:3].0” This assume lcore 2 and 3 are on different physical cores on the same socket. Note skipping lcore 0 for Linux and lcore 1 is used for Pktgen display and timers.

If you need two ports pktgen –l 1-5 –n 4 -- -m”[2:3].0, [4:5].1” 

>
>Thanks in advance,
>Mark
>




      reply	other threads:[~2016-06-23 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 10:33 Marko Niinimaki
2016-06-23 14:17 ` Wiles, Keith [this message]

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=231BE07A-F689-41BA-8852-D8E240DAAB59@intel.com \
    --to=keith.wiles@intel.com \
    --cc=manzikki@gmail.com \
    --cc=users@dpdk.org \
    /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).