I'm not sure whether it is the issue here but note about the Global Interprer Lock in CPython, see [1], [2]. The usual workaround is "fake threading" using multiprocessing module [3]. It is question how this would interact with MPI.
[1] http://en.wikipedia.org/wiki/CPython#Concurrency_issues [2] https://docs.python.org/2/library/threading.html [3] https://docs.python.org/2/library/multiprocessing.html Jan On Fri, 17 Oct 2014 11:58:12 +0200 Martin Sandve Alnæs <[email protected]> wrote: > How can I achieve an MPI barrier with a timeout? I'd like to start > some of the tests with garbage collection and an mpi barrier with a > timeout so we can exit semi-gracefully and report a point where > things fail. > > A workaround I can think of is to run MPI.barrier in a python thread > and poll that thread until a timeout and then die if it doesn't > return. I'm not concerned with the fallout when blowing up here (or > should I be?) because this would probably be better than a deadlock > and a later kill from the outside anyway. > > Martin _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
