From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 9EEE858FA for ; Sun, 1 Feb 2015 00:47:26 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 31 Jan 2015 15:47:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,498,1418112000"; d="scan'208";a="670887704" Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by fmsmga002.fm.intel.com with ESMTP; 31 Jan 2015 15:47:25 -0800 Received: from orsmsx159.amr.corp.intel.com (10.22.240.24) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 31 Jan 2015 15:47:23 -0800 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by ORSMSX159.amr.corp.intel.com (10.22.240.24) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 31 Jan 2015 15:47:23 -0800 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.154]) by FMSMSX154.amr.corp.intel.com ([169.254.6.103]) with mapi id 14.03.0195.001; Sat, 31 Jan 2015 15:47:23 -0800 From: "Wiles, Keith" To: "Wiles, Keith" , Bhavesh Davda Thread-Topic: [dpdk-dev] [PATCH] examples: new txburst application Thread-Index: AQHQPHhdL3ryJs/iiUOEKIlj0pZmM5zZYOiAgAAD9gCAAAGVAIAAMSEAgAFxhIA= Date: Sat, 31 Jan 2015 23:47:23 +0000 Message-ID: References: <1416335575-30717-1-git-send-email-bhavesh@vmware.com> <25405198.KkrSSHtStQ@xps13> <72e5096b3711419f93a9161a20c9fa11@EX13-MBX-025.vmware.com> <3621315.EODueA6DKm@xps13> <3AD66C8B-4AF4-494C-8CDE-85DFFDE16C15@intel.com> In-Reply-To: <3AD66C8B-4AF4-494C-8CDE-85DFFDE16C15@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.80.194] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <080EEE3E5C1F3949A19EE2B7012EAA9F@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] examples: new txburst application 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: Sat, 31 Jan 2015 23:47:27 -0000 On 1/30/15, 1:45 PM, "Wiles, Keith" wrote: > > >Sent from my iPhone > >On Jan 30, 2015, at 9:49 AM, Bhavesh Davda wrote: > >>> Did you know pktgen-dpdk? >>> http://dpdk.org/browse/apps/pktgen-dpdk/tree/README.md >>>=20 >>> Do you think it could replace your application? >>=20 >> [Bhavesh Davda] Yes, I regularly use pktgen-dpdk, and love the app >>(thanks Keith!) but I couldn't quite get it to do this simplistic job of >>generating a stream of X-byte UDP packets in burst of Y spread apart by >>Z microseconds. > >Hmmm, sounds like an enhancement request to pktgen is needed here. I will >look at adding it to pktgen and it is up to everyone if the example is >reasonable to have. For me it does seem reasonable to include as it maybe >simpler to setup, but if and when I can add that support to pktgen it may >no longer be needed. > >Let me have a look at adding the support and will let you guys know next >week. Looking at the txburst code and your description needing to send a burst of 220 byte UDP packets with an interval of 50us is mostly doable via Pktgen. In Pktgen you can setup a packet 220+UDP+other parameters already in single packet mode or sequence mode. You can set the rate at a given percentage per second of packets, but you can not set the interval rate between burst easily. The number of packets in a burst is also adjustable via the burst command =B9set burst '. Did I describe the problem here correctly? The current percentage rate is in whole numbers in Pktgen may not be fine enough gain rate for some tests. I do have in Pktgen a way to adjust the time between burst of packets using a debug command to fine tune the number of clock ticks (HPET) to a given number =B9set tx_cycles ', would that command be useful and solve your given test case? The tx_cycles option is not listed in the help text :-) Maybe I should make it not hidden. > >Thanks Keith