Re: [OMPI devel] RFC: Remove (broken) heterogeneous support

2013-01-30 Thread Siegmar Gross
Hi > WHAT: Remove the configure command line option to enable heterogeneous > support > > WHY: The heterogeneous conversion code isn't working, very few people > use this feature > > WHERE: README and config/opal_configure_options.m4. See attached patch. > > TIMEOUT: Next Tuesday teleconf, 5 F

Re: [OMPI devel] RFC: Remove (broken) heterogeneous support

2013-01-30 Thread Jeff Squyres (jsquyres)
On Jan 30, 2013, at 7:36 AM, Siegmar Gross wrote: > HiI have no problem with the option --enable-heterogeneous, when I build > Open MPI, but Open MPI will not work in a heterogeneous environment > with little and big endian machines, Right -- that's the issue: --enable-heterogeneous is broken (

Re: [OMPI devel] RFC: Remove (broken) heterogeneous support

2013-01-30 Thread Andreas Schäfer
On 14:36 Wed 30 Jan , Jeff Squyres (jsquyres) wrote: > On Jan 30, 2013, at 7:36 AM, Siegmar Gross > wrote: > > > HiI have no problem with the option --enable-heterogeneous, when I build > > Open MPI, but Open MPI will not work in a heterogeneous environment > > with little and big endian mac

Re: [OMPI devel] RFC: Remove (broken) heterogeneous support

2013-01-30 Thread Jeff Squyres (jsquyres)
On Jan 30, 2013, at 9:40 AM, Andreas Schäfer wrote: > But isn't heterogeneity the main reason for having MPI datatypes in > the first place? Otherwise I could always use MPI_CHAR and sizeof(Foo). Heterogeneity was a much bigger issue back in the 90s. Nowadays, most people have pretty homogeneo

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Jure Pečar
On Mon, 28 Jan 2013 12:28:34 -0800 Paul Hargrove wrote: > I will be happy to retest on both the XC30 and XE6 at NERSC from a nightly > tarball with the fixes. > Please give me a heads up when that is available. I'd be interested in that too. Hello all, sorry to hijack a thread, but I have to b

Re: [OMPI devel] RFC: opal_list iteration macros

2013-01-30 Thread KAWASHIMA Takahiro
Hi, Agreed. But how about backward traversal in addition to forward traversal? e.g. OPAL_LIST_FOREACH_FW, OPAL_LIST_FOREACH_FW_SAFE, OPAL_LIST_FOREACH_BW, OPAL_LIST_FOREACH_BW_SAFE We sometimes search an item from the end of a list. Thanks, KAWASHIMA Takahiro > What: Add two new macros to

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Nathan Hjelm
Try configuring with --with-platform=contrib/platform/lanl/cray_xe6/optimized-nopanasas . That might work. If it doesn't try the optimized-lustre file from the same directory in trunk. -Nathan On Wed, Jan 30, 2013 at 04:28:14PM +0100, Jure Pe??ar wrote: > On Mon, 28 Jan 2013 12:28:34 -0800 > P

Re: [OMPI devel] RFC: opal_list iteration macros

2013-01-30 Thread Nathan Hjelm
Hmm, maybe something like: OPAL_LIST_FOREACH, OPAL_LISTFOREACH_REV, OPAL_LIST_FOREACH_SAFE, OPAL_LIST_FOREACH_REV_SAFE? -Nathan On Thu, Jan 31, 2013 at 12:36:29AM +0900, KAWASHIMA Takahiro wrote: > Hi, > > Agreed. > But how about backward traversal in addition to forward traversal? > e.g. OPAL

Re: [OMPI devel] RFC: opal_list iteration macros

2013-01-30 Thread KAWASHIMA Takahiro
I don't care the macro names. Either one is OK for me. Thanks, KAWASHIMA Takahiro > Hmm, maybe something like: > > OPAL_LIST_FOREACH, OPAL_LISTFOREACH_REV, OPAL_LIST_FOREACH_SAFE, > OPAL_LIST_FOREACH_REV_SAFE? > > -Nathan > > On Thu, Jan 31, 2013 at 12:36:29AM +0900, KAWASHIMA Takahiro wrote

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Jure Pečar
On Wed, 30 Jan 2013 08:48:02 -0700 Nathan Hjelm wrote: > Try configuring with > --with-platform=contrib/platform/lanl/cray_xe6/optimized-nopanasas . That > might work. If it doesn't try the optimized-lustre file from the same > directory in trunk. > I used optimized-common. That fails with:

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Ralph Castain
I'm afraid that optimized-common doesn't stand alone - it requires other modules as well. If you look at optimized-lustre, you'll see that we include cray-common, optimized-common, and gnu-common, and then add the lustre flags. You need all three of those modules to build successfully. If you do

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Nathan Hjelm
Use the optimized-lustre. optimized-common is not intended to be used on its own. -Nathan On Wed, Jan 30, 2013 at 06:31:09PM +0100, Jure Pe??ar wrote: > On Wed, 30 Jan 2013 08:48:02 -0700 > Nathan Hjelm wrote: > > > Try configuring with > > --with-platform=contrib/platform/lanl/cray_xe6/optim

[OMPI devel] 1.6.4rc3 released

2013-01-30 Thread Jeff Squyres (jsquyres)
In the usual place: http://www.open-mpi.org/software/ompi/v1.6/ Changes since rc2: - Fix a seg fault in the openib BTL when no connection method can be found. This is looking pretty stable; it could well be the last rc. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go

Re: [OMPI devel] Open MPI (not quite) on Cray XC30

2013-01-30 Thread Jure Pečar
On Wed, 30 Jan 2013 10:09:09 -0800 Ralph Castain wrote: > I'm afraid that optimized-common doesn't stand alone - it requires other > modules as well. If you look at optimized-lustre, you'll see that we include > cray-common, optimized-common, and gnu-common, and then add the lustre flags. > >