1. 26 Feb, 2014 1 commit
  2. 25 Oct, 2012 1 commit
  3. 19 Oct, 2012 1 commit
  4. 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.
  5. 08 Mar, 2012 1 commit
  6. 20 Feb, 2012 1 commit
    • David Goodell's avatar
      [svn-r9511] implement MPIX_Mprobe and friends · a91381e9
      David Goodell authored
      This includes MPIX_Mprobe, MPIX_Improbe, MPIX_Mrecv, and MPIX_Imrecv.
      !!!NOTE!!! This change adds four more functions to the ADI.
      The current implementation of MPIX_Mprobe is much less efficient than it
      could be.  Right now it polls the unexpected queue (UQ), much like
      MPI_Probe does.  A better implementation would enqueue the "message"
      object on the PQ so that the matching is handled by the progress engine
      in the various packet handlers.  Unfortunately, such an implementation
      is surprisingly complicated at this point.
      Includes only a simple test for now (test/mpi/pt2pt/mprobe), but it at
      least shows that our Mprobe functionality basically all works.
      Reviewed by buntinas@.
  7. 21 Nov, 2011 1 commit
    • David Goodell's avatar
      [svn-r9202] very rough implementation of the MPI_T interface (as MPIX_T) · 4831e108
      David Goodell authored
      Most of the problems associated with this implementation have to do with
      initialization bootstrapping/teardown issues.  Using the new interface
      to profile MPI_Init/MPI_Finalize certainly has at least a few bugs right
      now.  Use entirely within an MPI_Init/MPI_Finalize region should
      basically work fine.
      Two performance variables are exposed right now, the expected and
      unexpected queue lengths.  All environment variables from the parameter
      interface are exposed via the new "control variable" API.
      No reviewer.