1. 19 May, 2015 2 commits
  2. 13 May, 2015 2 commits
  3. 11 May, 2015 2 commits
  4. 10 May, 2015 2 commits
  5. 05 May, 2015 2 commits
  6. 30 Apr, 2015 2 commits
  7. 29 Apr, 2015 5 commits
    • Rob Latham's avatar
      fixup: correctly const-ify hint processing routine · 66b5407a
      Rob Latham authored
      No reviewer
    • Rob Latham's avatar
      test case for large gather · cdf23c55
      Rob Latham authored
      see #1767
      Signed-off-by: Kenneth Raffenetti's avatarKen Raffenetti <raffenet@mcs.anl.gov>
    • Pavan Balaji's avatar
      Added support for static compilation. · d1413272
      Pavan Balaji authored
      If the user passes the -static flag, we disable interlibrary
      dependencies, since the linker would pick the static versions of the
      libraries in that case.
      We are still making an assumption that the default mode of the linker
      is shared, and the user can specify static library builds with
      -static.  However, this is not always true.  On BG/Q, for example, the
      default is static.
      Fixes #2190.
      Signed-off-by: Kenneth Raffenetti's avatarKen Raffenetti <raffenet@mcs.anl.gov>
    • Pavan Balaji's avatar
      Cleaned up the management of wrapper flags in MPICH. · 90100837
      Pavan Balaji authored
      This includes several changes:
      1. Merged WRAPPER and EXTERNAL LIBS.  There is no reason to maintain
      two names for these flags.  These are eventually appended and added to
      the compiler wrappers anyway.
      2. Updated mpicc and friend to add the necessary flags directly
      instead of trying to merge these flags in configure.
      Signed-off-by: Kenneth Raffenetti's avatarKen Raffenetti <raffenet@mcs.anl.gov>
    • Pavan Balaji's avatar
      Remove MPICHLIB_LDFLAGS/LIBS · 4d93cefa
      Pavan Balaji authored
      It does not make sense for the user to specify LDFLAGS/LIBS that would
      only be used to build the MPICH library, but not the user application.
      Doing do will create a false dependency of the MPICH library on these
      external libraries resulting in weird interactions with the user
      application in cases where interlibrary dependencies are not
      supported.  We were anyway silently modifying the WRAPPER LDFLAGS/LIBS
      to include these anyway, so the flags themselves were weirdly screwed
      This patch simply removes them instead of pretending to allow them,
      but not really allowing them.
      Signed-off-by: Kenneth Raffenetti's avatarKen Raffenetti <raffenet@mcs.anl.gov>
  8. 28 Apr, 2015 4 commits
  9. 27 Apr, 2015 5 commits
    • Valentin Petrov's avatar
      OFI: Bug fix for RTS/CTS/DATA protocol. · 2069c15e
      Valentin Petrov authored
      MPID_nem_ofi_data_callback used to check sreq->cc in order to track progress of
      the RTS/CTS/DATA protocol. The was an implicit assumption that fi_tsend with RTS
      completes first. However this would cause a hang if fi_trecv completed earlier.
      The fix is: don't rely on the cc but rather check the tag bits explicitly.
      Note, the RTS/CTS/DATA bits are no longer accumulated (i.e., no more
      "wc->tag | CTS/DATA").
      Signed-off-by: default avatarCharles J Archer <charles.j.archer@intel.com>
    • Valentin Petrov's avatar
      OFI: MPIR_Barrier_impl should not be called from MPID_nem_ofi_finalize. · 34e57aa8
      Valentin Petrov authored
      It uses nemesis shared memory which is already cleaned up at this stage.
      However, w/o any synchronization a hang in the close protocol is possible
      since rts/cts/data messages may be on the fly. This change fixes the issue.
      Signed-off-by: default avatarCharles J Archer <charles.j.archer@intel.com>
    • Valentin Petrov's avatar
    • Valentin Petrov's avatar
    • Valentin Petrov's avatar
      OFI: Add support for large tags using immediate data and OFI tag layouts · ec920e5f
      Valentin Petrov authored
      This patch modifies the OFI netmod to support large tag layouts, while preserving the old
      tag layout.  OFI defines a 64 bit tag, but also provides for a 64 bit tag and immediate data.
      In some OFI providers, we may want to select different tag layouts.  This patch currently
      does not query for the proper tag layout or attempt to make a choice of the optimal layout,
      it provides macro/templatized support for different tag formats.  Additional selection
      criteria will be added in subsequent patches.
        * Tag layout is moved to a separate file.
          Added init_sendtag_M2, init_recvtag_M2 (M2 stands for MODE #2, i.e. the mode
          that uses fi_tsenddata and does not pack source into tag).
        * Created a template file for ofi_tagged.c
          Moved do_isend into template file which is included twice into ofi_tagged.c thus providing for the two
          versions of do_isend and do_isend_2 corresponding to the two API sets.
        * All send functions are available in two versions.
          Added macro that declares a function for the two API sets. The first set has the namings inherited from
          the previous netmod version. The functions of the second API set have the "_2" suffix.
        * Recv_posted, anysource_posted, recv_callback, ofi_probe  are templatized.
        * ofi_tag_to_vc renamed ofi_wc_to_vc
          Note, for the API_SET_2 the pgid is stored in the imm data while
          psource and port will be packed the same way as in API_SET_1.
        * Adds api_set member in gl_data struct.  Initialize routines based on api_set
        * Added RCD (RtsCtsData) protocol identifiers
        * Added support for OFI MEM_TAG_FORMAT
        * PGID placement modified
      Signed-off-by: default avatarCharles J Archer <charles.j.archer@intel.com>
  10. 24 Apr, 2015 10 commits
  11. 23 Apr, 2015 3 commits
  12. 22 Apr, 2015 1 commit
    • Pavan Balaji's avatar
      Fix arbitrary poll count before yielding. · abb56764
      Pavan Balaji authored
      Instead of polling for an arbitrarily decided number of times in the
      progress engine before yielding, we now moved the yielding
      intelligence to the threading layer.  The threading layer can keep
      track of other threads that are waiting to enter the critical section
      and only yield if another thread is waiting.  In this way, if no
      thread is waiting to get the lock, the main thread never yields.  At
      the same time, if another thread is waiting to get a lock, there is no
      delay in yielding.
      This change, however, introduces possible deadlocks. If a thread enters
      MPIDI_CH3I_progress with is_blocking unset, it may set the
      MPIDI_CH3I_progress_blocked flag and then will yield the critical section.
      Another thread may enter with is_blocking set, find the flag
      MPIDI_CH3I_progress_blocked set, and block in the conditional variable.
      The first thread will wake up and leave the progress engine without
      emitting any signal to wake up the second thread which may sleep forever.
      A simple fix is to yield the critical section only if the current thread
      entered the progress engine with is_blocking set.
      Signed-off-by: default avatarHalim Amer <aamer@anl.gov>