Re: [dpdk-dev] [PATCH] ppc64: fix compilation of when AltiVec is enabled

["Pradeep Satyanarayana" <pradeep@us.ibm.com>]

Thomas Monjalon <thomas@monjalon.net> wrote on 11/05/2018 06:15:53 AM:

> From: Thomas Monjalon <thomas@monjalon.net>
> To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Cc: dev@dpdk.org, TYOS@jp.ibm.com, adrien.mazarguil@6wind.com,
> Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>, Chao
> Zhu <chaozhu@linux.vnet.ibm.com>, Luca Boccassi <bluca@debian.org>,
> Pradeep Satyanarayana <pradeep@us.ibm.com>, 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 <TYOS@jp.ibm.com>
> > 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=http-3A__mails.dpdk.org_archives_dev_2018-2DSeptember_110733.html&d=DwICAg&c=jf_iaSHvJObTbx-

> siA1ZOg&r=co4lCofxrQP11yIVMply-
>
QYvsUyeKJkYY_jL1QVgeGA&m=dMrH4GLoXWGcc5xt87goaWszBzO4TeTVx7O9pZo160o&s=_hNc10YMFL2mf2TkG9tbjm5_2fyPER3MswvK-

> NKs9RY&e=
>    - 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