Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD*(take 2)

2010-03-07 Thread Ralph Castain
On Mar 7, 2010, at 5:13 PM, Jeff Squyres wrote: > On Mar 7, 2010, at 12:59 PM, Ralph Castain wrote: > >> > Quick question about this. We now have an OPAL level progress thread, >> > which enables the machinery at the OPAL level. Unfortunately, this doesn't >> > say anything about what the MPI

Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD*(take 2)

2010-03-07 Thread Jeff Squyres
On Mar 7, 2010, at 12:59 PM, Ralph Castain wrote: > Quick question about this. We now have an OPAL level progress thread, which enables the machinery at the OPAL level. Unfortunately, this doesn't say anything about what the MPI level will do? That is correct and has always been the case.

Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD* (take 2)

2010-03-07 Thread Ralph Castain
Those are excellent questions that I have asked as well at various times :-) Some thoughts below On Mar 7, 2010, at 1:20 PM, George Bosilca wrote: > Quick question about this. We now have an OPAL level progress thread, which > enables the machinery at the OPAL level. Unfortunately, this doesn't

Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD* (take 2)

2010-03-07 Thread George Bosilca
Quick question about this. We now have an OPAL level progress thread, which enables the machinery at the OPAL level. Unfortunately, this doesn't say anything about what the MPI level will do? Moreover, this is quite confusing as there are no communications layers in OPAL so one can ask what an O

Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD* (take 2)

2010-03-05 Thread Ralph Castain
I'm not going to commit this today - I think it would be a little quick :-) However, I do have it all building on a Mercurial branch with the new options. It would be REALLY GOOD if people interested in thread support were to check this out prior to me bringing it to the trunk. The branch can b

Re: [OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD* (take 2)

2010-03-05 Thread Terry Dontje
A couple comments: 1. I really assume the timeout is March 5th not February. 2. As to keeping the deprecated variables I think you really need to ditch the --enable-mpi-threads because if you synonym it with --enable-mpi-thread-multiple you are not mimicing what it did before but redefining i

[OMPI devel] RFC: Rename --enable-*-threads and ENABLE*THREAD* (take 2)

2010-03-04 Thread Jeff Squyres
WHAT: Rename the --enable-*-threads configure switches and ENABLE*THREAD* macros. (see previous RFC: http://www.open-mpi.org/community/lists/devel/2010/01/7366.php) WHY: The fact that thread safety in OPAL and ORTE requires a configure switch with "mpi" in the name is very non-intuitive.