Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29055 - in trunk/ompi/mca: btl btl/smcuda common/cuda pml/ob1

2013-08-28 Thread George Bosilca
Rolf, I'm not arguing against the choices you made. I just want to pinpoint that there are other way of achieving a similar goal with less impact on the components outside of the SMCUDA BTL, an approach which might be interesting in the long run. Thus my answer below is just so there is a trace

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29079 - in trunk: opal/mca/hwloc/base orte/mca/rmaps/mindist

2013-08-28 Thread Ralph Castain
Please also change the name - it is being declared in a component, and thus the "base" should not be in the name On Aug 28, 2013, at 9:40 AM, Nathan Hjelm wrote: > Would something even more generic such as rmaps_base_dist_network_device > be better. Could update the code to detect Gemini or Are

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29079 - in trunk: opal/mca/hwloc/base orte/mca/rmaps/mindist

2013-08-28 Thread Nathan Hjelm
Would something even more generic such as rmaps_base_dist_network_device be better. Could update the code to detect Gemini or Ares for example. -Nathan On Wed, Aug 28, 2013 at 04:36:22PM +, Jeff Squyres (jsquyres) wrote: > Can we rename rmaps_base_dist_hca to something that is less specific t

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29079 - in trunk: opal/mca/hwloc/base orte/mca/rmaps/mindist

2013-08-28 Thread Joshua Ladd
I have no objections to this. Josh -Original Message- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Wednesday, August 28, 2013 12:37 PM To: Subject: Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29079 - in trunk: opal/mca/hwloc/base orte/mc

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r29079 - in trunk: opal/mca/hwloc/base orte/mca/rmaps/mindist

2013-08-28 Thread Jeff Squyres (jsquyres)
Can we rename rmaps_base_dist_hca to something that is less specific to IB? E.g., rmaps_base_dist_verbs_device? (admittedly, that's a little long, but...) On Aug 28, 2013, at 12:23 PM, wrote: > Author: jladd (Joshua Ladd) > Date: 2013-08-28 12:23:33 EDT (Wed, 28 Aug 2013) > New Revision: 290

Re: [OMPI devel] ompi_info

2013-08-28 Thread Jeff Squyres (jsquyres)
Actually, the compromise was listed in my original mail: 2a. Fair enough. The long-standing ompi_info behavior precedent alone is probably enough to warrant re-thinking the new ompi_info behavior. Nathan will implement a compromise (that George was ok with when I talked on the phone with hi

[OMPI devel] Possible OMPI 1.6.5 bug? SEGV in malloc.c

2013-08-28 Thread Chris Samuel
Hi folks, One of our users (oh, OK, our director, one of the Dalton developers) has found an odd behaviour of OMPI 1.6.5 on our x86 clusters and has managed to get a small reproducer - a modified version of the ubiquitous F90 "hello world" MPI program. We find that if we run this program (compile

Re: [OMPI devel] ompi_info

2013-08-28 Thread George Bosilca
Jeff is indeed correct, the compromise we reached was to default to the historical behavior of showing only the parameters of selected components and have an option to show everything else. George. PS: Shouldn't "ompi_info --param all all" be identical to "ompi_info --all"? On Aug 27, 2013,