From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by dpdk.org (Postfix) with ESMTP id 0FD9C4F90 for ; Mon, 5 Nov 2018 22:21:01 +0100 (CET) Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wA5LItJo037981 for ; Mon, 5 Nov 2018 16:21:01 -0500 Received: from smtp.notes.na.collabserv.com (smtp.notes.na.collabserv.com [192.155.248.81]) by mx0a-001b2d01.pphosted.com with ESMTP id 2njw2khjs5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 05 Nov 2018 16:21:00 -0500 Received: from localhost by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for from ; Mon, 5 Nov 2018 21:21:00 -0000 Received: from us1a3-smtp03.a3.dal06.isc4sb.com (10.106.154.98) by smtp.notes.na.collabserv.com (10.106.227.88) with smtp.notes.na.collabserv.com ESMTP; Mon, 5 Nov 2018 21:20:53 -0000 Received: from us1a3-mail95.a3.dal06.isc4sb.com ([10.146.21.14]) by us1a3-smtp03.a3.dal06.isc4sb.com with ESMTP id 2018110521205329-1181751 ; Mon, 5 Nov 2018 21:20:53 +0000 In-Reply-To: <2547699.pxo2WhrkVo@xps> To: Thomas Monjalon Cc: adrien.mazarguil@6wind.com, Luca Boccassi , Chao Zhu , Christian Ehrhardt , dev@dpdk.org, dwilder@us.ibm.com, TYOS@jp.ibm.com From: "Pradeep Satyanarayana" Date: Mon, 5 Nov 2018 13:20:51 -0800 References: <2547699.pxo2WhrkVo@xps> X-KeepSent: 7FCAED99:F10D4E80-8825833C:00726271; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0.1EXT SHF888 April 26, 2018 X-LLNOutbound: False X-Disclaimed: 32931 X-TNEFEvaluated: 1 x-cbid: 18110521-7093-0000-0000-000008FFD293 X-IBM-SpamModules-Scores: BY=0.26521; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.429909; ST=0; TS=0; UL=0; ISC=; MB=0.000707 X-IBM-SpamModules-Versions: BY=3.00009992; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000268; SDB=6.01113176; UDB=6.00577026; IPR=6.00893276; BA=6.00006137; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00024037; XFM=3.00000015; UTC=2018-11-05 21:20:59 X-IBM-AV-DETECTION: SAVI=unsuspicious REMOTE=unsuspicious XFE=unused X-IBM-AV-VERSION: SAVI=2018-11-05 19:43:25 - 6.00009182 x-cbparentid: 18110521-7094-0000-0000-00006E0325A4 Message-Id: MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-05_12:, , signatures=0 X-Proofpoint-Spam-Reason: safe X-Mailman-Approved-At: Tue, 06 Nov 2018 13:27:16 +0100 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: Quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] ppc64: fix compilation of when AltiVec is enabled 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, 05 Nov 2018 21:21:02 -0000 Thomas Monjalon wrote on 11/05/2018 06:15:53 AM: > From: Thomas Monjalon > To: Christian Ehrhardt > Cc: dev@dpdk.org, TYOS@jp.ibm.com, adrien.mazarguil@6wind.com, > Gowrishankar Muthukrishnan , Chao > Zhu , Luca Boccassi , > Pradeep Satyanarayana , dwilder@us.ibm.com > Date: 11/05/2018 06:16 AM > Subject: Re: [dpdk-dev] [PATCH] ppc64: fix compilation of when > AltiVec is enabled > > Hi, > > 30/08/2018 13:58, Christian Ehrhardt: > > On Thu, Aug 30, 2018 at 12:52 PM Takeshi T Yoshimura > > wrote: > > > Hi, > > > I could reproduce the issue you reported in 18.08 with my ppc64le box with > > > RedHat 7.5 and GCC4.8. > > > The patch resolved the issue in my environment. Thanks! > > > > I added your test (tanks) and Adrien's extensive review/discussion as tags > > and also addressed a few checkpatch findings. > > V2 is up on the list now ... > > > > > I am a bit newbie in dpdk-dev, but I will try contacting Chao and other > > > IBM guys... Sorry for our slow reply. > > > > Thanks for your participation Takeshi, > > we at least now have had a few replies after Thomas used the superpowers of > > "CPT. CAPSLOCK" \o/. > > > > I also have a call later today to make sure this is brought up inside IBM > > to make sure someone is maintaining it for real. > > Summary of the situation: > - I used caps lock on August 30th > - We got replies on the ML in the next 2 days (Alfredo, Chao, Takeshi) > - On September 3rd, Adrien raised a major issue for C++ with the fix v3 > INVALID URI REMOVED > u=3Dhttp-3A__mails.dpdk.org_archives_dev_2018-2DSeptember_110733.html&d=3DD= wICAg&c=3Djf_iaSHvJObTbx- > siA1ZOg&r=3Dco4lCofxrQP11yIVMply- > QYvsUyeKJkYY_jL1QVgeGA&m=3DdMrH4GLoXWGcc5xt87goaWszBzO4TeTVx7O9pZo160o&s=3D= _hNc10YMFL2mf2TkG9tbjm5_2fyPER3MswvK- > NKs9RY&e=3D > - Another email about a possible GCC fix on September 5th (David Wilder) As Dave mentioned that is only expected in GCC 9. > - There was a private reply on September 27th, confirming an IBM support > - and nothing else > > Nobody at IBM requests to get a compilation fix for ppc64. Yes, we do need fixes for ppc64. (1) http://mails.dpdk.org/archives/dev/2018-August/110499.html (2) http://mails.dpdk.org/archives/dev/2018-September/110961.html Based on the above 2 URLs (tested both by Takeshi and David Wiler), we assumed that it would get picked up in 18.11. We have been more focussed on 17.11 (and likely dropped the ball on 18.11) since 17.11 is an LTS release and we have had lots of problems on ppc64. Should be submitting patch to fix those issues shortly. We have built 18.11-rc1 with the fix above (1), and it does work on ppc64le. An updated version of: (3) http://mails.dpdk.org/archives/dev/2018-August/109926.html also builds on ppc64. The latter has the advantage of possibly not breaking existing applications. > And there was no issue raised after 18.11-rc1 release. > I guess it means DPDK is not used on ppc64. > In this case, we should mark the ppc port as unmaintained for 18.11. > > OR SHOULD I USE MY CAPS LOCK AGAIN? Thanks for your patience while we iron out the issues. Hopefully, we don't need the CAPS LOCK again. Thanks Pradeep pradeep@us.ibm.com