November 2009 - Mpich2-core - mailman3.cels.anl.gov

TRAC experimentation
by Pavan Balaji 24 Dec '09

24 Dec '09

All, I'm trying some experimentation with the mpich2 trac to see if we can allow users to just enter their email address on the new tickets page and not worry about logging in with OpenID, etc. I'm not sure if it'll be successful, but we'll see. This might result in some random tickets + possibly some spam getting through, but hopefully only for 1-2 days. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

3 8

Re: [mpich2-core] maint/updatefiles fails
by chan＠mcs.anl.gov 14 Dec '09

14 Dec '09

What version does your libtool claim to be. I had 2.2.4 and 2.2.6a on MCS machine and they works with updatefiles's autoreconf. I will try downgrading libtool to see if that works. A.Chan login3.surveyor:~/mpich_work > libtool --version ltmain.sh (GNU libtool) 2.2.6b login3.surveyor:~/mpich_work > libtoolize --version libtoolize (GNU libtool) 2.2.6b ----- "Darius Buntinas" <buntinas(a)mcs.anl.gov> wrote: > Sorry, I missed that. > > Try libtool --version > > For some reason even though I had 2.2.6b installed, it still claimed > to > be the old one. > > -d > > On 11/18/2009 01:26 PM, Anthony Chan wrote: > > I already have libtool 2.2.6b (see below) > > blueprint is AIX though. Surveyor is PPC linux. > > > > ----- "Darius Buntinas" <buntinas(a)mcs.anl.gov> wrote: > > > >> I got this same problem on blueprint. You'll need to install > libtool > >> 2.2.6b. > >> > >> -d > >> > >> On 11/18/2009 01:11 PM, Anthony Chan wrote: > >>> mpich2's maint/updatefiles failed on surveyor. > >>> Any clue what is missing.. ? > >>> > >>> A.Chan > >>> > >>> Found ./configure.in; executing make configure target > >>> (cd . && autoheader -I ./confdb && \ > >>> autoconf -I ./confdb ) > >>> running third-party initialization > >>> autoreconf: Entering directory `.' > >>> autoreconf: configure.ac: not using Gettext > >>> autoreconf: running: aclocal --force -I config -I m4 > >>> autoreconf: configure.ac: tracing > >>> autoreconf: configure.ac: not using Libtool > >>> autoreconf: running: /home/chan/autoconf/2.63/bin/autoconf > --force > >>> configure.ac:417: error: possibly undefined macro: > >> AC_LIBTOOL_WIN32_DLL > >>> If this token and others are legitimate, please use > >> m4_pattern_allow. > >>> See the Autoconf documentation. > >>> autoreconf: /home/chan/autoconf/2.63/bin/autoconf failed with > exit > >> status: 1 > >>> login3.surveyor:~/mpich_work/mpich2 > which autoconf > >>> /home/chan/autoconf/2.63/bin/autoconf > >>> login3.surveyor:~/mpich_work/mpich2 > which automake > >>> /home/chan/automake/1.11/bin/automake > >>> login3.surveyor:~/mpich_work/mpich2 > which libtool > >>> /home/chan/libtool/2.2.6b/bin/libtool

5 8

FW: Converged API documentation
by Rajeev Thakur 09 Dec '09

09 Dec '09

This is the documentation on XMI. We should give them some feedback on this. The information is confidential. Rajeev -----Original Message----- From: Robert Wisniewski [mailto:[email protected]] Sent: Thursday, November 19, 2009 10:34 AM To: seager(a)llnl.gov; bronis(a)llnl.gov; beckman(a)mcs.anl.gov; smc(a)mcs.anl.gov; rbair(a)anlmail.anl.gov; lusk(a)mcs.anl.gov; thakur(a)mcs.anl.gov; KAYelick(a)lbl.gov; JShalf(a)lbl.gov Cc: Sameer Kumar; Brian Smith; Pat McCarthy Subject: Converged API documentation Please find attached a presentation and documentation on the current state of the converged API. This is IBM confidential and may still be changing. If you have feedback please let us know. Also please distribute as appropriate to others at your sites making sure to let them know it is still confidential. Thank you. -bob Robert Wisniewski Manager Blue Gene Software IBM T. J. Watson Research Center 914-945-3181 http://www.research.ibm.com/people/b/bob/ bobww(a)us.ibm.com

3 2

Re: [mpich2-core] MPI on The Register
by jayesh＠mcs.anl.gov 30 Nov '09

30 Nov '09

>> you tell the network upfront, when this request completes, do this next one (very similar to Erez's async executive stuff, but in hardware) FWIW, Erez's async executive engine doesn't have any request chaining capability. It is actually a different design take on what we had with sock util (mpid/common/sock/iocp) on windows. -Jayesh ----- Original Message ----- From: "Pavan Balaji" <balaji(a)mcs.anl.gov> To: mpich2-core(a)mcs.anl.gov Sent: Thursday, November 26, 2009 12:00:43 PM GMT -06:00 US/Canada Central Subject: Re: [mpich2-core] MPI on The Register Looks like they are going the Quadrics way, which probably means that they are going to go bankrupt as well :-). I heard about this from the Mellanox folks. If I understood it correctly, it was a firmware based (not true hardware) solution for barrier, broadcast and integer reduce. Btw, Mellanox also came up with a "collective offload" solution for their network adapters, which is nothing more than work request chaining, i.e., you tell the network upfront, when this request completes, do this next one (very similar to Erez's async executive stuff, but in hardware). Also, came to know from Gilad that Oak Ridge had given them a lot of money for the collective offload chip (ConnectX2) under the condition that OSU can't publish the work before they do :-). Rich had some preliminary numbers which were terrible; but I'm sure some workshop will accept it. -- Pavan On 11/26/2009 09:57 AM, Rob Ross wrote: > Some discussion of this "collective acceleration in IB switches": > http://www.theregister.co.uk/2009/11/26/sc09_networking_wrapup/ > > What's the scoop on that? > > Rob > > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

MPI on The Register
by Rob Ross 26 Nov '09

26 Nov '09

Some discussion of this "collective acceleration in IB switches": http://www.theregister.co.uk/2009/11/26/sc09_networking_wrapup/ What's the scoop on that? Rob

3 3

C89++ for MPICH2
by Pavan Balaji 24 Nov '09

24 Nov '09

For as long as MPICH/MPICH2 has been developed, we have always tried to maintain the code as C89 compatible as possible. This is, in general, a good idea. However, this required us to add a lot of code to work with platforms and compilers that don't have C99 support. Given that C99 is almost a decade old now, and most compilers today support it, I'd like to initiate a discussion to see what people's thoughts are on requiring "C89++" support from the compiler for MPICH2. By C89++, I mean C89 together with a few features from C99. My initial list contains just two features with some reasoning: 1. snprintf -- this will allow us to totally get rid of MPIU_Snprintf given that it is not complete anyway, but only provides a handful of options. 2. __VA_ARGS__ -- this will allow us to remove the requirement to add FUNCNAME for each function we add and a lot of code that checks if VA_ARGS is defined before doing anything with it. If there are other C99 features that would be useful, please point them out as well. It goes without saying that the configure will of course still check if these exist. However, if they are not found, instead of trying to fall back to some other internal implementation, it'll abort. If you are against this approach, it'll be helpful if you can point out systems/compilers where it might be a problem. If you support this change, please do point that out as well. Thanks, -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

6 9

SDSC rocks
by Pavan Balaji 24 Nov '09

24 Nov '09

It looks like SDSC Rocks is shipping with Open MPI (through Sun Cluster tools). Who do we know at SDSC who works on Rocks? How do we get MPICH2 in there? -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

3 4

mpich-1 website
by Pavan Balaji 24 Nov '09

24 Nov '09

Should we redirect the MPICH-1 website to the new MPICH2 page? http://www.mcs.anl.gov/research/projects/mpi/mpich1 -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

4 3

Re: [mpich2-core] Fwd: Please update Absoft listing on MPICH2 page
by chan＠mcs.anl.gov 24 Nov '09

24 Nov '09

Hi Wood Lotz, I was able to build mpich2 with the absoft 10.1 compiler with following configure variables set: CC=gcc CXX=g++ F77=af77 F90=af90 and to compile/run simple MPI fortran 77 code fine. So it seems that U77 library isn't really needed to build mpich2, so I would think we could leave libU77.a out for users to link in by themselves. Can you confirm that ? A.Chan ----- "Rusty Lusk" <lusk(a)mcs.anl.gov> wrote: > Begin forwarded message: > > > From: Wood Lotz <wlz(a)absoft.com> > > Date: November 24, 2009 10:37:59 AM CST > > To: lusk(a)mcs.anl.gov > > Cc: bitter(a)mcs.anl.gov > > Subject: Please update Absoft listing on MPICH2 page > > > > > > Rusty, > > > > Further search of your site did locate Absoft build instructions for > > > MPICH2, however they are out of date. Please update them with > > updated instructions below. > > > > Existing / Old: > > Q: How do I configure to use the Absoft Fortran compilers? > > > > http://wiki.mcs.anl.gov/mpich2/index.php/Frequently_Asked_Questions > > > > > > Updated > > Updated build instructions for MPICH2 for 32-bit and 64-bit Linux > > and Mac OS are available on our site at: > > > http://www.absoft.com/Products/Compilers/Fortran/Linux/fortran95/MPich_Inst… > > Also, the Absoft Pro Fortran F95 compiler has been extended to > > include F77 extensions and the F77 compiler is no longer include > > effective v10.0 and later. > > > > Build instructions for x64 Linux and Absoft Fortran v10.1 and later > > > is shown below: > > > > Linux 64 bit, Absoft Fortran 95 10.1 and Later > > 1) Extract the MPICH2 source and change to the extracted source > > directory: > > tar -xzvf mpich2-1.0.6p1.tar.gz > > cd mpich2-1.0.6p1 > > 2) Configure MPICH2 with the following command: > > ./configure F77=$ABSOFT/bin/f77 \ > > FFLAGS="-lU77" \ > > F90=$ABSOFT/bin/f90 \ > > F90FLAGS="-lU77" > > 3) Build MPICH2: > > make > > 4) Install MPICH2: > > make install > > > > Thank you for your help on this matter. > > Please let us know if you have any additional questions. > > > > Regards, > > > > Wood Lotz > > > > > > > >> Hello Rusty, > >> > >> It as been a while since we exchanged emails. > >> > >> I am writing from Absoft to see if you would add Absoft Fortran to > > >> the list (gnu, Intel and pgi) of Fortran compilers listed on your > > >> MPICH2 page: > http://wiki.mcs.anl.gov/mpich2/index.php/Testing_MPICH2 > >> > >> We are updating our site to include additional information, > >> references and links for customers interested in building clusters. > > >> We plan to put a link to your MPICH2 page and would like to see > >> Absoft listed on it - rather than just the competition. Currently > > >> we have build instructions for MPICH2 on our site for reference: > http://www.absoft.com/Products/Compilers/Fortran/Linux/fortran95/BuildingMP… > >> > >> Please let me know if you have any questions. > >> > >> Thank you. > >> > >> Wood Lotz > >> > > > > -- > > > > > > Wood Lotz > > > > Absoft Corporation 2781 Bond Street Rochester Hills, MI 48309 USA > > (248) 853-0050 - voice (248) 853 0108 - fax www.absoft.com > > 28 years of Software Leadership, Innovation & Performance Fortran, > C+ > > + compilers & debugging solutions for Windows, OS X & Linux > >

1 0

Fwd: Please update Absoft listing on MPICH2 page
by Rusty Lusk 24 Nov '09

24 Nov '09

Begin forwarded message: > From: Wood Lotz <wlz(a)absoft.com> > Date: November 24, 2009 10:37:59 AM CST > To: lusk(a)mcs.anl.gov > Cc: bitter(a)mcs.anl.gov > Subject: Please update Absoft listing on MPICH2 page > > > Rusty, > > Further search of your site did locate Absoft build instructions for > MPICH2, however they are out of date. Please update them with > updated instructions below. > > Existing / Old: > Q: How do I configure to use the Absoft Fortran compilers? > > http://wiki.mcs.anl.gov/mpich2/index.php/Frequently_Asked_Questions > > > Updated > Updated build instructions for MPICH2 for 32-bit and 64-bit Linux > and Mac OS are available on our site at: > http://www.absoft.com/Products/Compilers/Fortran/Linux/fortran95/MPich_Inst… > Also, the Absoft Pro Fortran F95 compiler has been extended to > include F77 extensions and the F77 compiler is no longer include > effective v10.0 and later. > > Build instructions for x64 Linux and Absoft Fortran v10.1 and later > is shown below: > > Linux 64 bit, Absoft Fortran 95 10.1 and Later > 1) Extract the MPICH2 source and change to the extracted source > directory: > tar -xzvf mpich2-1.0.6p1.tar.gz > cd mpich2-1.0.6p1 > 2) Configure MPICH2 with the following command: > ./configure F77=$ABSOFT/bin/f77 \ > FFLAGS="-lU77" \ > F90=$ABSOFT/bin/f90 \ > F90FLAGS="-lU77" > 3) Build MPICH2: > make > 4) Install MPICH2: > make install > > Thank you for your help on this matter. > Please let us know if you have any additional questions. > > Regards, > > Wood Lotz > > > >> Hello Rusty, >> >> It as been a while since we exchanged emails. >> >> I am writing from Absoft to see if you would add Absoft Fortran to >> the list (gnu, Intel and pgi) of Fortran compilers listed on your >> MPICH2 page: http://wiki.mcs.anl.gov/mpich2/index.php/Testing_MPICH2 >> >> We are updating our site to include additional information, >> references and links for customers interested in building clusters. >> We plan to put a link to your MPICH2 page and would like to see >> Absoft listed on it - rather than just the competition. Currently >> we have build instructions for MPICH2 on our site for reference: http://www.absoft.com/Products/Compilers/Fortran/Linux/fortran95/BuildingMP… >> >> Please let me know if you have any questions. >> >> Thank you. >> >> Wood Lotz >> > > -- > > > Wood Lotz > > Absoft Corporation 2781 Bond Street Rochester Hills, MI 48309 USA > (248) 853-0050 - voice (248) 853 0108 - fax www.absoft.com > 28 years of Software Leadership, Innovation & Performance Fortran, C+ > + compilers & debugging solutions for Windows, OS X & Linux >

1 0