This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
After some searching, it turns out mpi4py tries to call MPI_Init_thread but python in general has issues with threads apparently. I'm backing off from threading at this point.
From: TERRY DONTJE <terry.dontje_at_[hidden]>
Sent: Wednesday, January 11, 2012 8:09 AM
Subject: Re: [OMPI users] using MPI_Recv in two different threads.
I am a little confused by your problem statement. Are you saying you want to have each MPI process to have multiple threads that can call MPI concurrently? If so you'll want to read up on the MPI_Init_thread function.
On 1/11/2012 7:19 AM, Hamilton Fischer wrote:
Hi, I'm actually using mpi4py but my question should be similar to normal MPI in spirit. Simply, I want to do a MPMD application with a dedicated thread for each node (I have a small network). I was wondering if it was okay to do a blocking recv in each independent thread. Of course, since each thread has one node, there is no problem with wrong recv's being picked up by other threads. Thanks. noobermin _______________________________________________
users mailing list users_at_[hidden] http://www.open-mpi.org/mailman/listinfo.cgi/users
Terry D. Dontje | Principal Software Engineer
Developer Tools Engineering | +1.781.442.2631
Oracle - Performance Technologies
95 Network Drive, Burlington, MA 01803
users mailing list