From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 9330A71B3 for ; Thu, 11 Jan 2018 23:31:25 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EB85720C90; Thu, 11 Jan 2018 17:31:24 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 11 Jan 2018 17:31:24 -0500 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=SoNSTzmYZ9KCdbtKNoVS2S95D1 iE0w9hqjg92vifjo0=; b=FTbfnHNoujhO4hQM/Ld5LIIC8iCtQMLoaBxGk2j0lH P4CUpEJ5wk+YM88BNHSqiYS3/V0qDyb5yWIz4Z6CxKAhD9QydyIHYSCtm/kp3h2B Jp4ftAjKfQS8ql/awf9Kjgi/nMuT8t8mSIMWtUztMTsdHH3rKmG0ZEuL72BUORmU E= 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=fm1; bh=SoNSTz mYZ9KCdbtKNoVS2S95D1iE0w9hqjg92vifjo0=; b=YqbJ4fhyesvGsRcl6XGBDn 3bpJIPgHxAJQfh7aFDUxSV+r04eBjdDmUUSOm6ETyVJ1pY8/SqgVJuuaYwKRiX+P 04WxpeUphkfDtuEygPl7fFmUX+tO1DfbLlQHYew6yPASmQOzH2D/U+9GAXfIfB3e p0gJV8toxNhB4lbCBMlKzDnmQs2xvGoP/Uu/N2WUUOBiz5/dl7Fbjvr0VGFrVFlm URMvg0d1IYC4dhO+huXERrfGXg/ByeCmt7oqqs6Xs7KvjxqhOofuInhJUdsAIYsP cMEZuQHdfG2/Uobc7Pm/DGECx4bTwv7ZTf+PWc1br547DgwIvwOYyc+U5joE+7FA == 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 90AE97E536; Thu, 11 Jan 2018 17:31:24 -0500 (EST) From: Thomas Monjalon To: Harry van Haaren Cc: dev@dpdk.org, Pavan Nikhilesh , bruce.richardson@intel.com Date: Thu, 11 Jan 2018 23:30:56 +0100 Message-ID: <1681790.YjdVV9QU4d@xps> In-Reply-To: <20180110102318.vpswoqnqrnqzznjb@Pavan-LT> References: <1515497885-191922-1-git-send-email-harry.van.haaren@intel.com> <1515505061-12112-1-git-send-email-harry.van.haaren@intel.com> <20180110102318.vpswoqnqrnqzznjb@Pavan-LT> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 1/2] service: fix lcore role after delete 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, 11 Jan 2018 22:31:25 -0000 10/01/2018 11:23, Pavan Nikhilesh: > On Tue, Jan 09, 2018 at 01:37:40PM +0000, Harry van Haaren wrote: > > This patch fixes the reset of the service core, > > that when rte_service_lcore_del() is called, the > > lcore_role is restored to RTE. > > > > This issue was reported as when running the unit tests, an > > error was thrown that "failed to allocate lcore". Investigating > > revealed that the state of the service-cores after del() was > > not allowing a core to be re-used at a later point in time. > > > > Fixes: 21698354c832 ("service: introduce service cores concept") > > +CC stable@dpdk.org The canonical format is: Cc: stable@dpdk.org > > Reported-by: Pavan Nikhilesh > > Signed-off-by: Harry van Haaren > > Series-Acked-by: Pavan Nikhilesh Applied, thanks