From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BAFC9A00E6 for ; Wed, 10 Jul 2019 15:19:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1EC00324D; Wed, 10 Jul 2019 15:19:07 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 9784B2B99 for ; Wed, 10 Jul 2019 15:19:05 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jul 2019 06:19:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,474,1557212400"; d="scan'208";a="170916835" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga006.jf.intel.com with ESMTP; 10 Jul 2019 06:19:04 -0700 Received: from fmsmsx125.amr.corp.intel.com (10.18.125.40) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 10 Jul 2019 06:19:03 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.206]) by FMSMSX125.amr.corp.intel.com ([169.254.2.73]) with mapi id 14.03.0439.000; Wed, 10 Jul 2019 06:19:04 -0700 From: "Wiles, Keith" To: Sara Gittlin CC: "users@dpdk.org" Thread-Topic: [dpdk-users] pktgen w pcap file Thread-Index: AQHVNyEzuxR438iFlkOZV2u2lPca4qbESysA Date: Wed, 10 Jul 2019 13:19:02 +0000 Message-ID: <117A28F3-51CD-4A6B-9BC1-6EC14F346147@intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.251.155.216] Content-Type: text/plain; charset="us-ascii" Content-ID: <4FD7A2CF39411C408562B9C3AD7667A8@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] pktgen w pcap file X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" The way Pktgen works is it loads the packets into memory until it fills up = the number of buffers allocated, which I think is 8192 buffers. If you pcap= file is more then that they are ignored. Pktgen has different modes for the transmitting packets, the PCAP is loaded= and assign to a port, but it doe not mean they will be sent. The default m= ode is single packet mode and you have to enable PCAP file to be sent using= the enable pcap command. Then you have to do a start = on that port to send the pcap files. Each mode has its own set of buffers = it can send, so you can switch to modes and be able to reenable pcap mode o= n a port to send the pcap buffers again. The pcap data loaded into memory will be sent over and over if you send mor= e than the number of pcap packets you loaded. The way DPDK works it possibl= e they will be send out of order :-( > On Jul 10, 2019, at 8:12 AM, Sara Gittlin wrote: >=20 > Hi all > I'm running the pkgen w pcap file , -s P:http.pcap > but i dont see any pkts in the receive side > Is pktgen automatically transmits the pcap after startup ? or i have to > manually run it from the cli ? > is it possible to run this pcap many times? > Thank you > -Sara Regards, Keith