From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal/ppc: remove fix of memory barrier for IBM POWER Date: Thu, 28 Mar 2019 18:56:50 +0100 Message-ID: <18284767.dla22OQ03R@xps> References: <1552913893-43407-1-git-send-email-dekelp@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit 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 To: Pradeep Satyanarayana 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) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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