Gabriele,
If you want to write portable MPI applications then I think you should
stick with what the standard say. In other words for hybrid
programming, and if only one thread will make MPI calls you need
either MPI_THREAD_FUNNELED or MPI_THREAD_SERIALIZED.
Now, that being said, I don't
Hi George.
So is it dangerous to use hybrid program ( MPI+OpenMP) without enable
threads support?
2008/9/29 George Bosilca
> Gabriele,
>
> The thread support has to be explicitly requested at build time, or it will
> be disabled. Add --enable-mpi-threads (configure --help will give you more
> in
Gabriele,
The thread support has to be explicitly requested at build time, or it
will be disabled. Add --enable-mpi-threads (configure --help will give
you more info) to your configure. If you plan to use threads with Open
MPI I strongly suggest to update to the 1.3. This version is not yet
Another question about MPI_INIT_THREAD.
At the moment, as said, my OpenMPi version supports only level 0:
MPI_THREAD_SINGLE. Suppose that i have this code:
#pragma omp barrier
#pragma omp master
MPI_Send(buf,...);
#pragma omp barrier
Due my OpenMPI configuration, is it dangerous use this
Dear OpenMPi developers,
i've noted that OpenMPI 1.25 and 1.2.6 version doesn't supports thread
initialization function shows below:
int MPI_Init_thread(int *argc, char *((*argv)[]), int required, int
*provided)
used in hybrid programming MPI+OpenMP. Returned vales provided is 0, so the
unique
