From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id F0B4F8E98 for ; Thu, 21 Jan 2016 20:01:13 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 7D0F3FC; Thu, 21 Jan 2016 14:01:13 -0500 (EST) Date: Thu, 21 Jan 2016 14:01:13 -0500 From: Matthew Hall To: "Wiles, Keith" Message-ID: <20160121190113.GC10170@mhcomputing.net> References: <56A07787.2040807@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PKTGEN] dumb question: how to start packet TX and set the payload 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: Thu, 21 Jan 2016 19:01:14 -0000 On Thu, Jan 21, 2016 at 03:01:33PM +0000, Wiles, Keith wrote: > The problem is you used the same core (2) for the -m option. Core 2 is being > used for the keyboard, timer and screen output. This means you must have the > -m option starting with core 3 as in -m 3.0 and your problem should go away. > The first or master core is consume by Pktgen to handle the previous stuff > and you must start with the next cores for Rx/Tx of packets. I really need > to put tests in the code, which I will try to add soon. I'll see if I can figure out some patches for that. Matthew.