DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Paul Tsvika <mozloverinweb@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [pktgen] pktgen Tx/Rx rates are not the same in loopback testing case
Date: Fri, 21 Jul 2017 15:40:47 +0000	[thread overview]
Message-ID: <D81B7535-D384-4981-8B8B-A4F6C760C983@intel.com> (raw)
In-Reply-To: <CAGi_MX=XPUVKT-yUnD_F7FiF8qzgSQN1HFVF1vyKq90yKo0=5A@mail.gmail.com>


> On Jul 21, 2017, at 10:11 AM, Paul Tsvika <mozloverinweb@gmail.com> wrote:
> 
> Hi developers,

Attachements at scrubbed from emails to the list, so best to add links or inline the text.

What is the core layout for your system. Can you run the cpu-layout.py tool.

> 
> Below is my hardware configuration:
> 
> Memory: 32G ( 16 G on two channels )
> CPU: Xeon-D 1557 ( 12 cores, hyperthreading - 24 core )
> NIC: Intel X552/X557 10GBASE-T
> 
> My motherboard has 2 10G ports so that I set up the testing experiment in
> loopback.
> 
> I have compiled DPDK successfully and below is the steps how I configured
> pktgen
> 
> $ sudo modprobe uio
> $ sudo insmod ./build/kmod/igb_uio.ko
> $ sudo ./usertools/dpdkdevbind.py -b igb_uio xxx:xx.0 xxx:xx.1
> $ sudo ./app/pktgen -c 0x1f -n 2 -- -P -m "[1:3].0, [2:4].1"
> <pktgen> start 0
> 
> I use core 1 and core 3 work for port 0 tx/rx respectively. Core 2 and core
> 4 work for port 1 tx/rx respectively.
> 
> I have some questions listed below:
> 
> 1.
> ​​( check my attachment d2.png )
> The TX rate is almost 10G, however, the RX rate is much lower than TX rate.
> I suppose this should not happen. Is my configuration wrong in any place ?
> I checked other developers and TX rate normally can reach 999x and RX rate
> is almost the same as TX rate.
> 
> 2.
> 
> Please check the attachment ( start_log ).
> 
> 2.1
> *Packet Burst 32, RX Desc 512, TX Desc 1024*, mbufs/port 8192, mbuf cache
> 1024
> Is 32 the default packet size ? How can I configure it to 64 ?
> Why RX Desc is different to TX Desc ?
> 
> 2,2
> *Port  0: Link Down <Enable promiscuous mode>*
> Port  1: Link Up - speed 10000 Mbps - full-duplex <Enable promiscuous mode>
> 
> Port 0 is down at some points, how can I check the root cause to this issue?
> 
> 
> 
> Thanks
> 
> -- 
> P.T
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: d2.png
> Type: image/png
> Size: 108971 bytes
> Desc: not available
> URL: <http://dpdk.org/ml/archives/users/attachments/20170721/c22e7dbe/attachment.png>

Regards,
Keith


  reply	other threads:[~2017-07-21 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 15:11 Paul Tsvika
2017-07-21 15:40 ` Wiles, Keith [this message]
2017-07-22  1:49   ` Paul Tsvika
2017-07-25  9:04     ` Paul Tsvika
2017-07-25 14:10       ` Wiles, Keith
2017-07-26  9:02         ` Paul Tsvika
2017-07-26 14:55           ` Wiles, Keith
2017-07-26 16:44     ` 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=D81B7535-D384-4981-8B8B-A4F6C760C983@intel.com \
    --to=keith.wiles@intel.com \
    --cc=mozloverinweb@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).