Re: [OMPI devel] still supporting pgi?

[Larry Baker]

On 11 Dec 2014, at 2:12 PM, Paul Hargrove wrote:

> I believe Larry Baker of USGS is also a PGI user (in production, rather than 
> just testing as I do). 


That is correct.

Although we are running a rather old Rocks cluster kit (CentOS based) which is 
so old that we cannot run the latest PGI releases.  Some time after the first 
of the year I plan to update Rocks and PGI and Intel and Oracle and GNU.  I'm 
giving up on PathScale and AMD/Open64.  I have already updated all the cluster 
firmware.  I just get side tracked.

Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov

Re: [OMPI devel] still supporting pgi?

[Paul Hargrove]

Howard,

I regularly test release candidates against the PGI installations on
NERSC's systems (and sometimes elsewhere).  In fact, have a test of
1.8.4rc2 against pgi-14.4 "in the pipe" right now.

I believe Larry Baker of USGS is also a PGI user (in production, rather
than just testing as I do).

-Paul

On Thu, Dec 11, 2014 at 1:34 PM, Jeff Squyres (jsquyres)  wrote:

> Howard --
>
> One thing I neglected to say -- if libfabric/usnic support on master is
> causing problems for you, you can configure without libfabric:
>
> ./configure --without-libfabric ...
>
> (which will, of course, also disable anything that requires libfabric)
>
> The intent is that we build things by default so that we can get at least
> smoke testing of as many features as possible -- especially testing that
> they don't interfere with others.  But we tend to put in options to shut
> off such things if they *do* cause problems.  Right now, libfabric is
> causing a few problems for you, so you should feel free to disable it until
> we figure out the integration problems (and if you could send me the
> details, I can have a look at what's going wrong).
>
> I'm sorry; I should have mentioned this earlier, but I assumed you knew
> about it / keep forgetting that you're still kinda new to our community and
> don't know all the conventions that we typically put in place!
>
> My bad.  :-(
>
>
>
> On Dec 11, 2014, at 10:45 AM, Jeff Squyres (jsquyres) 
> wrote:
>
> > On Dec 11, 2014, at 9:58 AM, Howard Pritchard 
> wrote:
> >
> >> Okay, I'll try to fix things.  problem in opal_datatype_internal.h,
> then a meltdown with libfabric owing to the fact that its probably
> >> only been used in a gnu env.  I'll open an issue on that one and assign
> it to Jeff.
> >
> > Ok.
> >
> > FWIW: I test with gcc and the intel compiler suite.  I do not have a PGI
> license to test with.
> >
> >> I think we should be turning this libfabric build off unless one asks
> for it.
> >
> > Obviously, I disagree.  :-)
> >
> > I'm sorry for the annoyances, but we have long since found out that
> features that are not enabled by default do not get tested in the wild and
> therefore do not get debugged.
> >
> > If you send me the details of the PGI problem, I'll be happy to look in
> to it.
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16511.php
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] still supporting pgi?

[Jeff Squyres (jsquyres)]

Howard --

One thing I neglected to say -- if libfabric/usnic support on master is causing 
problems for you, you can configure without libfabric:

./configure --without-libfabric ...

(which will, of course, also disable anything that requires libfabric)

The intent is that we build things by default so that we can get at least smoke 
testing of as many features as possible -- especially testing that they don't 
interfere with others.  But we tend to put in options to shut off such things 
if they *do* cause problems.  Right now, libfabric is causing a few problems 
for you, so you should feel free to disable it until we figure out the 
integration problems (and if you could send me the details, I can have a look 
at what's going wrong).

I'm sorry; I should have mentioned this earlier, but I assumed you knew about 
it / keep forgetting that you're still kinda new to our community and don't 
know all the conventions that we typically put in place!  

My bad.  :-(



On Dec 11, 2014, at 10:45 AM, Jeff Squyres (jsquyres)  
wrote:

> On Dec 11, 2014, at 9:58 AM, Howard Pritchard  wrote:
> 
>> Okay, I'll try to fix things.  problem in opal_datatype_internal.h, then a 
>> meltdown with libfabric owing to the fact that its probably
>> only been used in a gnu env.  I'll open an issue on that one and assign it 
>> to Jeff.   
> 
> Ok.
> 
> FWIW: I test with gcc and the intel compiler suite.  I do not have a PGI 
> license to test with.
> 
>> I think we should be turning this libfabric build off unless one asks for it.
> 
> Obviously, I disagree.  :-)
> 
> I'm sorry for the annoyances, but we have long since found out that features 
> that are not enabled by default do not get tested in the wild and therefore 
> do not get debugged.
> 
> If you send me the details of the PGI problem, I'll be happy to look in to it.
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] still supporting pgi?

[Paul Kapinos]

Jeff,
PGI compiler(s) are available on our Cluster:

$ module avail pgi

there are a lot of older versions, too:
$ module load DEPRECATED
$ module avail pgi


best

Paul


P.S. in our standard environmet, Intel compieler and Open MPI are active, so

$ module unload openmpi intel
$ module load pgi

P.S. We also have Sun/Oracle Studio:
$ module avail studio



On 12/11/14 19:45, Jeff Squyres (jsquyres) wrote:

Ok.

FWIW: I test with gcc and the intel compiler suite.  I do not have a PGI 
license to test with.



--
Dipl.-Inform. Paul Kapinos   -   High Performance Computing,
RWTH Aachen University, IT Center
Seffenter Weg 23,  D 52074  Aachen (Germany)
Tel: +49 241/80-24915



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [OMPI devel] still supporting pgi?

[Jeff Squyres (jsquyres)]

On Dec 11, 2014, at 9:58 AM, Howard Pritchard  wrote:

> Okay, I'll try to fix things.  problem in opal_datatype_internal.h, then a 
> meltdown with libfabric owing to the fact that its probably
> only been used in a gnu env.  I'll open an issue on that one and assign it to 
> Jeff.   

Ok.

FWIW: I test with gcc and the intel compiler suite.  I do not have a PGI 
license to test with.

> I think we should be turning this libfabric build off unless one asks for it.

Obviously, I disagree.  :-)

I'm sorry for the annoyances, but we have long since found out that features 
that are not enabled by default do not get tested in the wild and therefore do 
not get debugged.

If you send me the details of the PGI problem, I'll be happy to look in to it.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] still supporting pgi?

[Howard Pritchard]

Okay, I'll try to fix things.  problem in opal_datatype_internal.h, then a
meltdown with libfabric owing to the fact that its probably
only been used in a gnu env.  I'll open an issue on that one and assign it
to Jeff.

I think we should be turning this libfabric build off unless one asks for
it.

Howard


2014-12-11 7:42 GMT-08:00 Jeff Squyres (jsquyres) :
>
> On Dec 11, 2014, at 7:40 AM, Ralph Castain  wrote:
>
> > I’m unaware of any conscious decision to cut pgi off - I think it has
> been more a case of nobody having a license to use for testing.
>
> +1
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16504.php
>

Re: [OMPI devel] still supporting pgi?

[Nathan Hjelm]

On Thu, Dec 11, 2014 at 07:37:17AM -0800, Howard Pritchard wrote:
>Hi Folks,
>I'm trying to use mtt on a cluster where it looks like the only functional
>compiler that
>1) can build open mpi master
>2) can also build the ibm test suite
>may be pgi.  Can't compile write now, so I'm trying to fix it.  But I'm
>now wondering
>whether we are still supporting building open mpi with pgi compilers?  I'm
>using pgi
>14.4.

It *should* work but it really depends on if pgi fixed any of the
libnuma problems we complained about years ago. They have (had?) an
internal broken version of libnuma they use for their OpenMP stuff. We
had to build with -Mnoopenmp to get it to work at all. I got so fed up
with pgi that I dropped all support for using it with Open MPI on
Cielo. That said, now that pgi is part of nvidia things may be better
now.

I would check with HPC-3 and see how they build with pgi on our other
systems.

-Nathan


pgpFidnsg0l2w.pgp
Description: PGP signature

Re: [OMPI devel] still supporting pgi?

[Jeff Squyres (jsquyres)]

On Dec 11, 2014, at 7:40 AM, Ralph Castain  wrote:

> I’m unaware of any conscious decision to cut pgi off - I think it has been 
> more a case of nobody having a license to use for testing.

+1

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] still supporting pgi?

[Ralph Castain]

I’m unaware of any conscious decision to cut pgi off - I think it has been more 
a case of nobody having a license to use for testing.

> On Dec 11, 2014, at 7:37 AM, Howard Pritchard  wrote:
> 
> Hi Folks,
> 
> I'm trying to use mtt on a cluster where it looks like the only functional 
> compiler that
> 
> 1) can build open mpi master
> 2) can also build the ibm test suite
> 
> may be pgi.  Can't compile write now, so I'm trying to fix it.  But I'm now 
> wondering
> whether we are still supporting building open mpi with pgi compilers?  I'm 
> using pgi
> 14.4.
> 
> Thanks,
> 
> Howard
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/12/16502.php

[OMPI devel] still supporting pgi?

[Howard Pritchard]

Hi Folks,

I'm trying to use mtt on a cluster where it looks like the only functional
compiler that

1) can build open mpi master
2) can also build the ibm test suite

may be pgi.  Can't compile write now, so I'm trying to fix it.  But I'm now
wondering
whether we are still supporting building open mpi with pgi compilers?  I'm
using pgi
14.4.

Thanks,

Howard