From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E984D1B3B9 for ; Thu, 28 Mar 2019 18:56:54 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EA2BC221DC; Thu, 28 Mar 2019 13:56:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 28 Mar 2019 13:56:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=m3OLMY8IP0wF5UAMDJkrwAHuJy2eMCWVHoaW0w/gTHc=; b=sh9qbDdyX2s/ 2Yr5zu8rW03IkqIEl5DEA1ukBdpDqGVh5BfRCqifUzibMUZMnkELxNslfIdTzyIv gteM6dzfesSvmqmzFGCVAfK1tXHQGlBAmoTI5aqVkSwDWzdy56neOq79vnDiwWrg wvbc7IQEYGgFZI0+bBcLAZ3vKv1URsE= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=m3OLMY8IP0wF5UAMDJkrwAHuJy2eMCWVHoaW0w/gT Hc=; b=HlXMQaMArlxWWbZreRnJgI+FJi3B1pc24fo6Ld0ELMkFOgOIbyeBUb1c1 SCfUy5o/V000LNXu787/klCV62fbEwAZdk6/sdT4LBG4EuO9dW2l0508HvkpgRFq 1Ar6oRDI8oFKIT7yTZkIRFmc//zYlqFponYNZ0eXnNLUnIZxAf4imBzYIV0iGVv7 gefFLZaf89z6TOvNTBQttEHlfdgHRTGS0LnxlQ496HautOnOU36UYbIOOH61bjvj EfxQ3TH2esTbStr+bUX6JyYgkHABAqmVHzP0GoVWbrX7XeNK5ehGbm/VnJliyuba j3o2JGNi0aOYmWG9DbaYgMGBNC8pQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeeggddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 497ABE49FB; Thu, 28 Mar 2019 13:56:51 -0400 (EDT) From: Thomas Monjalon To: Pradeep Satyanarayana Cc: "bruce.richardson@intel.com" , Chao Zhu , Dekel Peled , dev@dpdk.org, David Christensen , "honnappa.nagarahalli@arm.com" , Idan Werpoler , "konstantin.ananyev@intel.com" , "ola.liljedahl@arm.com" , Olga Shern , Ori Kam , Shahaf Shuler , David Wilder , Yongseok Koh Date: Thu, 28 Mar 2019 18:56:50 +0100 Message-ID: <18284767.dla22OQ03R@xps> In-Reply-To: References: <1552913893-43407-1-git-send-email-dekelp@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal/ppc: remove fix of memory barrier for IBM POWER 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, 28 Mar 2019 17:56:55 -0000 28/03/2019 18:51, Pradeep Satyanarayana: > From: Pradeep Satyanarayana/Beaverton/IBM > > From: Thomas Monjalon > > > Pradeep, Chao, > > > > > > Do we have more news? > > > We must merge this patch for DPDK 19.05-rc1. > > > > > > I understand you want to try improving performance > > > by using lightweight sync for SMP barrier, > > > and this change can be done later. > > > First priority is to fix the bug of the general barrier. > > > That's why I should push this patch before the end of the week. > > > Dekel's patch at: > > > > http://mails.dpdk.org/archives/dev/2019-March/126746.html > > > > seems to be holding up well with the testing done so far. We have > > also pulled that patch in to test with DTS. If all hold up well, > > we should be able to let you know by tomorrow morning (US west coast > time). > > Thomas, > > This is to confirm that the internal testing has completed and all the > tests > passed. So, yes, we can push that into 19.05-rc1. > > We will have another patch out for the smp barriers as well. That is still > being tested. > > We will also need to get these patches into 18.11 and higher releases. We > will work with others to get that done. OK, thanks From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id EFC0FA0679 for ; Thu, 28 Mar 2019 18:56:57 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8FF831B3E0; Thu, 28 Mar 2019 18:56:56 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E984D1B3B9 for ; Thu, 28 Mar 2019 18:56:54 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EA2BC221DC; Thu, 28 Mar 2019 13:56:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 28 Mar 2019 13:56:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=m3OLMY8IP0wF5UAMDJkrwAHuJy2eMCWVHoaW0w/gTHc=; b=sh9qbDdyX2s/ 2Yr5zu8rW03IkqIEl5DEA1ukBdpDqGVh5BfRCqifUzibMUZMnkELxNslfIdTzyIv gteM6dzfesSvmqmzFGCVAfK1tXHQGlBAmoTI5aqVkSwDWzdy56neOq79vnDiwWrg wvbc7IQEYGgFZI0+bBcLAZ3vKv1URsE= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=m3OLMY8IP0wF5UAMDJkrwAHuJy2eMCWVHoaW0w/gT Hc=; b=HlXMQaMArlxWWbZreRnJgI+FJi3B1pc24fo6Ld0ELMkFOgOIbyeBUb1c1 SCfUy5o/V000LNXu787/klCV62fbEwAZdk6/sdT4LBG4EuO9dW2l0508HvkpgRFq 1Ar6oRDI8oFKIT7yTZkIRFmc//zYlqFponYNZ0eXnNLUnIZxAf4imBzYIV0iGVv7 gefFLZaf89z6TOvNTBQttEHlfdgHRTGS0LnxlQ496HautOnOU36UYbIOOH61bjvj EfxQ3TH2esTbStr+bUX6JyYgkHABAqmVHzP0GoVWbrX7XeNK5ehGbm/VnJliyuba j3o2JGNi0aOYmWG9DbaYgMGBNC8pQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeeggddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 497ABE49FB; Thu, 28 Mar 2019 13:56:51 -0400 (EDT) From: Thomas Monjalon To: Pradeep Satyanarayana Cc: "bruce.richardson@intel.com" , Chao Zhu , Dekel Peled , dev@dpdk.org, David Christensen , "honnappa.nagarahalli@arm.com" , Idan Werpoler , "konstantin.ananyev@intel.com" , "ola.liljedahl@arm.com" , Olga Shern , Ori Kam , Shahaf Shuler , David Wilder , Yongseok Koh Date: Thu, 28 Mar 2019 18:56:50 +0100 Message-ID: <18284767.dla22OQ03R@xps> In-Reply-To: References: <1552913893-43407-1-git-send-email-dekelp@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] eal/ppc: remove fix of memory barrier for IBM POWER 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190328175650.a3IS3xssnvi8TJOe186cVJAhkI_ZQBe0owDZPDDih3g@z> 28/03/2019 18:51, Pradeep Satyanarayana: > From: Pradeep Satyanarayana/Beaverton/IBM > > From: Thomas Monjalon > > > Pradeep, Chao, > > > > > > Do we have more news? > > > We must merge this patch for DPDK 19.05-rc1. > > > > > > I understand you want to try improving performance > > > by using lightweight sync for SMP barrier, > > > and this change can be done later. > > > First priority is to fix the bug of the general barrier. > > > That's why I should push this patch before the end of the week. > > > Dekel's patch at: > > > > http://mails.dpdk.org/archives/dev/2019-March/126746.html > > > > seems to be holding up well with the testing done so far. We have > > also pulled that patch in to test with DTS. If all hold up well, > > we should be able to let you know by tomorrow morning (US west coast > time). > > Thomas, > > This is to confirm that the internal testing has completed and all the > tests > passed. So, yes, we can push that into 19.05-rc1. > > We will have another patch out for the smp barriers as well. That is still > being tested. > > We will also need to get these patches into 18.11 and higher releases. We > will work with others to get that done. OK, thanks