From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by dpdk.org (Postfix) with ESMTP id 0DF345A81 for ; Wed, 28 Jan 2015 17:20:08 +0100 (CET) X-AuditID: c6180641-f79916d00000623a-5a-54c8ad242ed2 Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id F3.C1.25146.42DA8C45; Wed, 28 Jan 2015 10:34:28 +0100 (CET) Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0195.001; Wed, 28 Jan 2015 11:20:07 -0500 From: Alexandre Frigon To: "Wodkowski, PawelX" , "dev@dpdk.org" , "keith.wiles@windriver.com" Thread-Topic: Pktgen-DPDK rate and traffic inconsistency problem Thread-Index: AdA6TAAeo7ZX5X/gQHqE2Z04+NrY+AAthovAAANT3vA= Date: Wed, 28 Jan 2015 16:20:06 +0000 Message-ID: <3C433001F624134981FFEE5BA9665CCC081783@eusaamb107.ericsson.se> References: <3C433001F624134981FFEE5BA9665CCC081157@eusaamb107.ericsson.se> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.9] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyuXSPn67K2hMhBntbVC3efdrOZHHkzQ9W i6mnvrE6MHv8WrCU1WPxnpdMHuu3bGUKYI7isklJzcksSy3St0vgyth8/ThjwUmJimv9j9ka GM8KdTFyckgImEjsvjCZBcIWk7hwbz1bFyMXh5DAEUaJmbs62UASQgLLGSV2n2EGsdkEzCQ2 7zrMDlIkItDHKNG+ZQZYQljAXuLKr3lgk0QEHCTenF3EDmFbSTR3dYPFWQRUJV5f/Qk2lFfA W2JDw3VGiG1TGSUebG1m6mLk4OAUCJHob/IDqWEEuuj7qTVMIDazgLjErSfzmSAuFZBYsuc8 M4QtKvHy8T9WCFtRYl//dHaIeh2JBbs/sUHY2hLLFr5mhtgrKHFy5hOWCYyis5CMnYWkZRaS lllIWhYwsqxi5CgtTi3LTTcy3MQIjJFjEmyOOxgXfLI8xCjAwajEw2vw4HiIEGtiWXFl7iFG aQ4WJXHesisHQ4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwhjfH39irf/+vyqLsCQeDllsZ WW8On94pfva7dcjlf/FSD694uuy+s4zd68i9rSxTfz62fh0iMnHStOOX+v/dU4o6XylzRvAS +8yEH7X57+4/urXwkar04ZX7f5/6dWDJT/nkbQw7EyLStzzbE8oRdaeEe9mCx3mVSxSri0I+ TVVcsXrVWvVHh+qUWIozEg21mIuKEwHojJeCcgIAAA== Subject: Re: [dpdk-dev] Pktgen-DPDK rate and traffic inconsistency problem X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2015 16:20:09 -0000 Hi Pawel, Thanks for your reply. Sadly, assigning 1 core per port didn't change anything. As for the NUMA nodes, If I understand correctly there is a node for each s= ocket and I'm only using 1 socket with 4 cores and lscpu is showing me only= 1 node. I don't think I can do anything about that. Correct me if I'm wron= g on this one. I'm definitely going to try a older version and see if it works properly. Thanks for your help Alexandre F. > -----Original Message----- > From: Wodkowski, PawelX [mailto:pawelx.wodkowski@intel.com] > Sent: Wednesday, January 28, 2015 9:15 AM > To: Alexandre Frigon; dev@dpdk.org; keith.wiles@windriver.com > Subject: RE: Pktgen-DPDK rate and traffic inconsistency problem >=20 > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alexandre Frigon > > Sent: Tuesday, January 27, 2015 8:31 PM > > To: dev@dpdk.org > > Subject: [dpdk-dev] Pktgen-DPDK rate and traffic inconsistency problem > > > > Hi all, > > > > I'm using dpdk 1.8 and pktgen-dpdk 2.8 to generate traffic on a > > back-to-back setup both equipped with 82599EB 10-Gigabit NIC. > > The problem is when I start it, pktgen indicates 10000Mbits/s Tx with > > 64B packet size, but I'm receiving about 15% of it on the other end. > > This percentage seems to be proportional with the packet size. > > > > e.g. > > Using nload to read Rx traffic > > Pktgen: Tx: 10000Mbits/s =3D=3D> Other end: Rx 1660 > Mbits/s > > Rate: 100% > > Pkt size: 64B > > > > > > e.g 2 > > Pktgen: Tx: 10000Mbits/s =3D=3D> Other end: Rx 9385 > Mbits/s > > Rate: 100% > > Pkt size: 1518B > > > > > > Pktgen is started with this command on a Xeon(R) CPU E31270 @ 3.40GHz > > ./app/pktgen -c 1f -n 3 --proc-type auto --socket-mem 1024 > > --file-prefix pg -- -p > > 0x3 -P -N -m "[1:3].0, [2:4].1" >=20 > From past experience I don't assign more than 1 core per port. It had som= e > race conditions issues and one core I capable to RX or TX full 10G. > Also check if you assign proper cores/memory for your NICs (the same > NUMA node). >=20 > > > > Is there something I'm not configuring correctly or something I have mi= ss? > > > > Also, the % rate is acting strangely since anything above 50% doesn't > > change the Tx rate and anything below is modifying it > > e.g Tx: 10000Mbits/s 5000Mbits/s > > %Rate: >=3D50% 25% > > > > >=20 > Actually I am getting exactly opposite results :) If I set rate to 50% I = get > MBits/s Rx/Tx : 0/9942 9942/0 9942/994= 2 >=20 > For 10%: > MBits/s Rx/Tx : 0/1997 1997/0 1997/199= 7 >=20 > Which is about 2x set :D >=20 > Additionaly I am getting message when "start 0" -> "stop 0" -> "start 0" = is > issued > PMD: ixgbe_dev_rx_init(): forcing scatter mode >=20 > So there is definitely something wrong there but don't know where. > Another issue I encountered is build system that fail when building out-o= f- > tree. >=20 > Till this is fixed you can try version 2.7.1 that is working for me. >=20 > Pawel