DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shailja Pandey <csz168117@iitd.ac.in>
To: "Wiles, Keith" <keith.wiles@intel.com>, dev@dpdk.org
Subject: [dpdk-dev]  DPDK-pktgen not giving expected throughput
Date: Thu, 11 Jan 2018 10:20:26 +0530	[thread overview]
Message-ID: <cb9ef3c6-0d7c-85da-d9ad-c47e20095363@iitd.ac.in> (raw)

The command line for Pktgen is-

./app/app/x86_64-native-linuxapp-gcc/pktgen -c 0xfff -n 4 -- -T -P -m "[2].0,[4].1,[8].2,[10].3"

Configuration of the machine is-

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 63
Model name:            Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
Stepping:              2
CPU MHz:               1204.226
CPU max MHz:           3400.0000
CPU min MHz:           1200.0000
BogoMIPS:              5195.08
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31

Linux XeonE5 4.4.0-93-generic

Thanks!





>/On Jan 10, 2018, at 7:36 AM, Shailja Pandey <csz168117 at iitd.ac.in 
<https://dpdk.org/ml/listinfo/dev>> wrote: />//>/Hi, />//>/We are performing experiments on Dell Poweredge R430 server, which is 
based on Haswell architecture based xeon-2640 v3 processor. We have 
attached XL 710 NIC(2x40 GbE) to the machine and expect 59 Mpps packet 
generation per port. But pktgen is able to generate only 21 Mpps per 
port and we are not sure about the problem. />//>/We are using DPDK version 16.07 and DPDK-pktgen version 3.1.0. Is there 
any way to generate packets from pktgen at 118 Mpps ? /
What is the command line for Pktgen?

Using a single CPU you should be able to generate about 21Mpps, which tells me the configuration is not correct.

Pktgen needs N number of TX and RX cores to generate more traffic, plus the packets need to be spread across the cores using RSS. This means pktgen needs to be setup to generate packets with the 5 tuple difference to get all of the cores to receive the packets.

I need to know the command line and the configuration of the machine to help.
>//>/-- />//>/Thanks, />/Shailja />//
Regards,
Keith

-- 

Thanks,
Shailja

             reply	other threads:[~2018-01-11  5:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11  4:50 Shailja Pandey [this message]
2018-01-11  6:45 ` Shailja Pandey
2018-01-11 13:52   ` Wiles, Keith
  -- strict thread matches above, loose matches on Subject: below --
2018-01-25  8:56 Shailja Pandey
2018-01-25 15:39 ` Wiles, Keith
2018-01-13 18:51 Shailja Pandey
2018-01-13 20:49 ` Wiles, Keith
2018-01-10 13:36 Shailja Pandey
2018-01-10 13:56 ` Wiles, Keith

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=cb9ef3c6-0d7c-85da-d9ad-c47e20095363@iitd.ac.in \
    --to=csz168117@iitd.ac.in \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    /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).