From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 4233E8D35 for ; Thu, 26 Apr 2018 17:41:37 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B144F21B36; Thu, 26 Apr 2018 11:41:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 26 Apr 2018 11:41:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=0UdQtkkONRY8X5ZNz/yWd0wqGb 7srRMUGhz7FQPiuRI=; b=ZEak6Fwaw4q8kPIWvgCercH+Q9Am94iGNJoRgm3ctc xd8A0OvlyExvhRc1gg/lEWZgjW6Cdc8iSvkZswbrkTsw5MbxcJLo+yfTU+2hkpnd 4dvWUaB46aqkohEXvnOxpiVtfY3HyyiKFrwmeltzxMoHwPubnC+47anr5IOrjNdF M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=0UdQtk kONRY8X5ZNz/yWd0wqGb7srRMUGhz7FQPiuRI=; b=nNLfR2QiBbx2WRu3A8FoUr 2QPY23yY7Nplr+m4hIySvtxYVk+Ybhw1Z3shyfS22MdlPmeHiw/JEzk52u27k353 GpVT+qlpHadPrQJixEiP0qMw4mrdO/BMtdWBb6mQrfSqEtXVAVrzxv9IVF0cFF4o 9x64DNB1EBqY4w2Ad4/2LdOCHoftPiLHS+6h9Q0EXYSAzBoMs9MUyn0hU7myXKE7 kypfZuTTLnKxLReYtmBjL8e8K3dLeZ+U6V6YXGiLIVLmDq6NVFVGtrku8NzbWPdO /s7kKTHPl6/3iDuJgAmrmpmlWu9h4NjyCvsfS4pDFCEqCFPiMms6pPg00MS7gUlA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DFDF8E49E9; Thu, 26 Apr 2018 11:41:35 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, "Burakov, Anatoly" , Stephen Hemminger Date: Thu, 26 Apr 2018 17:41:34 +0200 Message-ID: <2061996.ruHfFoTWGj@xps> In-Reply-To: <442b5582-a593-bf6a-67a8-36109094088d@intel.com> References: <20180426004839.4097-1-sthemmin@microsoft.com> <442b5582-a593-bf6a-67a8-36109094088d@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal: shut up warning about master lcore X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2018 15:41:37 -0000 26/04/2018 09:44, Burakov, Anatoly: > On 26-Apr-18 1:48 AM, Stephen Hemminger wrote: > > This message looks suspicious and seen on healthy testpmd. > > EAL: WARNING: Master core has no memory on local socket! > > > > The message is wrong: the master lcore is 0 and its socket is 0 > > and there are multiple available memory segments on socket 0. > > > > At that point in the startup process, the count value is zero, > > meaning they are not used yet so the check_socket gets confused. > > > > Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists") > > Signed-off-by: Stephen Hemminger > > --- > > Was aware of this and going to fix it myself, but higher priority items > popped up. Thanks for fixing this! > > Acked-by: Anatoly Burakov Applied, thanks