Any comments on this? We wanted to clean up MPI_THREAD_MULTIPLE
support in the trunk and port these changes back to 1.5.x, but it's
unclear to me what our expectations should be about any
MPI_THREAD_MULTIPLE test succeeding. How do we assess (test) our
changes? Or, should we just hardwire thread support to be off, as we
have done with progress threads?
-------- Original Message --------
I've been assigned CMR 2728, which is to apply some thread-support
changes to 1.5.x. The trac ticket has amusing language about "needs
testing". I'm not sure what that means. We rather consistently say
that we don't promise anything with regards to true thread support. We
specifically say certain BTLs are off limits and we say things are
poorly tested and can be expected to break. Given all that, what does
it mean to test thread support in OMPI?
One option, specifically in the context of this CMR, is to test only
configuration options and so on. I've done this.
Another possibility is to confirm that simple run-time tests of
multi-threaded message passing succeed. I'm having trouble with this.
Attached is a simple test. It passes over sm but fails over TCP. (One
or both of the initial messages is not received.)
How high should I set my sights on this?
mpicc -xopenmp -m64 -O5 main.c
mpirun -np 2 --mca btl self,sm ./a.out
mpirun -np 2 --mca btl self,tcp ./a.out
devel mailing list
- text/x-csrc attachment: main.c