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 7EF71D018 for ; Tue, 17 Apr 2018 01:08:36 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 007DB20E79; Mon, 16 Apr 2018 19:08:35 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 16 Apr 2018 19:08: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=tYBePrlvAF2A6Bl9C2Ay5YhFgZ S+XmFzRQhTC9SBbKU=; b=cRS7kTpc38DH/b/xze9I5n9EsqU+/8zPFVIxVXt9sw 0pvshUG5Qkk7ivK/oLTaGzMkusHGyN8Ra25lj6Dp/zgB35eS2/VoJ3zNEBc1G83J N52nhW/sicc8eYVUAiLDDasQhbCUqdkKzk/fJxxi9c6X0L7efwahTJBfOmSQThQM k= 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=tYBePr lvAF2A6Bl9C2Ay5YhFgZS+XmFzRQhTC9SBbKU=; b=N95UXgvr+o3Nx4E9clsUVk fXqIVlsDDnTOrTpgPiBD/mawfEd0/ytwPooJKtuvb6DOrdBpeiPrmLWaig/a6Lcu QXPjfMaM4UliKzwuy6BU97GJiOpn9nMiRBZrcuxRlgkTA+wY2WQDVfJD66NHCJmy 1QtatvWch9TQln3UfGYhCvQ4Fp7quQyK6KaY6Y5cjBngp17NdPJ+mwe/l/d3IFPy Zdh8WfRGoZO5v+11w1tfMVmVE0PtdcjjRsGOhXZG5/wRFGzWqnajMPX3yVU4sZ/a TRYfMcIU3AvnaPsCUMAIfl6rW57//I2FnRzKbnZu6/JeO8rPBAR8i2V++ruA9RYw == 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 61605E47A1; Mon, 16 Apr 2018 19:08:35 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, "Tan, Jianfeng" Date: Tue, 17 Apr 2018 01:08:33 +0200 Message-ID: <4392448.9KZnxiq8cY@xps> In-Reply-To: References: <864a5b05e83e899437daafc5610dca890b6e020d.1523373832.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] eal/ipc: stop async IPC loop on callback request 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: Mon, 16 Apr 2018 23:08:36 -0000 13/04/2018 17:24, Tan, Jianfeng: > > On 4/10/2018 11:28 PM, Anatoly Burakov wrote: > > EAL did not stop processing further asynchronous requests on > > encountering a request that should trigger the callback. This > > resulted in erasing valid requests but not triggering them. > > > > Fix this by stopping the loop once we have a request that > > can trigger the callback. Once triggered, we go back to scanning > > the request queue until there are no more callbacks to trigger. > > > > Fixes: f05e26051c15 ("eal: add IPC asynchronous request") > > Cc: anatoly.burakov@intel.com > > > > Signed-off-by: Anatoly Burakov > > Acked-by: Jianfeng Tan Applied, thanks