1
1
openmpi/opal/threads
Brian Barrett b56c8c3a66 * Default the value of opal_uses_threads (which is used by the macro
versions of the thread lock functions to determine at runtime if a lock
  is needed) to OMPI_ENABLE_PROGRESS_THREADS instead of 
  OMPI_HAVE_THREAD_SUPPORT.  Opal only starts a thread when
  OMPI_ENABLE_PROGRESS_THREADS is enabled, and ORTE never really starts
  a thread that requires special locking considerations.

  MPI_INIT would set opal_uses_threads to true if thread level was 
  greater than MPI_THREAD_SINGLE, but it would never decreast the
  value of opal_uses_threads, meaning that we always enabled all that
  locking if we did a threaded build, which isn't neccessary.  Now
  we do locking iff progress threads are enabled OR thread level
  is above MPI_THREAD_SINGLE.

This commit was SVN r11390.
2006-08-24 13:57:26 +00:00
..
condition.c Next step in the project split, mainly source code re-arranging 2006-02-12 01:33:29 +00:00
condition.h Windows friendly version. We have to split the OMPI_DECLSPEC in at least 3 2006-08-20 15:54:04 +00:00
Makefile.am Update the copyright notices for IU and UTK. 2005-11-05 19:57:48 +00:00
mutex_unix.h Latest and greatest. Now OPAL is ready for the Windows prime-time. 2006-08-23 00:29:35 +00:00
mutex_windows.h Windows friendly version. We have to split the OMPI_DECLSPEC in at least 3 2006-08-20 15:54:04 +00:00
mutex.c * Default the value of opal_uses_threads (which is used by the macro 2006-08-24 13:57:26 +00:00
mutex.h Latest and greatest. Now OPAL is ready for the Windows prime-time. 2006-08-23 00:29:35 +00:00
thread.c Correctly handle the basic operations on threads. 2006-08-22 17:55:36 +00:00
threads.h Latest and greatest. Now OPAL is ready for the Windows prime-time. 2006-08-23 00:29:35 +00:00