1. 07 Jan, 2014 1 commit
    • Pavan Balaji's avatar
      Make SMP-awareness in MPI_Barrier consistent. · 4f977797
      Pavan Balaji authored
      
      
      The current implementation of SMP-awareness in MPI_Barrier was in
      MPIR_Barrier_impl.  This makes the default implementation of barrier
      SMP-aware.  However, if a device overrides barrier and then calls back
      the default implementation through MPIR_Barrier, it can no longer take
      advantage of SMP-awareness.  This patch moves the SMP-aware
      implementation to MPIR_Barrier_intra, which is called by
      MPIR_Barrier_impl through MPIR_Barrier, in the default implementation.
      See #1957.
      Signed-off-by: default avatarMichael Blocksome <blocksom@us.ibm.com>
      4f977797
  2. 19 Dec, 2013 1 commit
  3. 26 Oct, 2013 1 commit
  4. 25 Jul, 2013 1 commit
  5. 17 May, 2013 2 commits
  6. 05 Nov, 2012 1 commit
    • Pavan Balaji's avatar
      [svn-r10546] Several manpage corrections: · 60f9b7bf
      Pavan Balaji authored
      1. Make the manpage entries consistent with the function prototype.
      
      2. Consistently use "Parameters" instead of the inconsistent
      "Parameter" and "Parameters" usage.
      
      3. Correct the manpages for MPI_Type_get_contents and
      MPI_Type_get_envelope.
      
      Reviewed by dinan.
      60f9b7bf
  7. 10 Oct, 2012 1 commit
  8. 20 Sep, 2012 1 commit
    • Pavan Balaji's avatar
      [svn-r10247] Get rid of duplicate jump on failure for the MPIR_ERRTEST_ macros. · 06397126
      Pavan Balaji authored
      In several places, after checking for a parameter (e.g., comm) we were
      directly using it assuming that the parameter is valid.  Since the
      previous ERRTEST macros did not jump to fn_fail on an error, this
      could result in undefined behavior if the parameter was invalid.  Now,
      since we jump on errors within the macros themselves, once the check
      is done, we know that the parameter values are valid.
      
      Reviewed by buntinas.
      06397126
  9. 25 Jul, 2012 1 commit
  10. 21 May, 2012 1 commit
  11. 24 Apr, 2012 2 commits
  12. 21 Jan, 2011 2 commits
  13. 13 Jan, 2011 1 commit
    • Darius Buntinas's avatar
      [svn-r7720] Fix collectives to not hang if the communicator contains a failed... · 3e71b782
      Darius Buntinas authored
      [svn-r7720] Fix collectives to not hang if the communicator contains a failed process.  The collectives will not return an error immediately upon detecting a failure, rather they'll return the error at the end of the function and continue the communication pattern so that other processes waiting to receive messages will not hang.  This means that, although the collective should complete at all processes, some processes will receive an error, and some processes may not get a valid result.  Since some processes may not receive an error and still receive an invalid result, a separate mechanism is needed to confirm that the collective has completed correctly, such as MPI_Comm_validate of the MPI3 FT proposal.
      3e71b782
  14. 30 Sep, 2010 1 commit
  15. 09 Jun, 2010 1 commit
  16. 08 Jun, 2010 1 commit
  17. 17 Sep, 2009 1 commit
  18. 12 May, 2009 1 commit
  19. 20 Jan, 2009 1 commit
  20. 09 Oct, 2008 1 commit
  21. 08 Oct, 2008 1 commit
  22. 07 Oct, 2008 1 commit
  23. 22 Sep, 2008 1 commit
  24. 02 Nov, 2007 1 commit