1. 30 May, 2015 1 commit
  2. 27 May, 2015 1 commit
  3. 20 May, 2015 1 commit
  4. 10 Apr, 2015 1 commit
    • Kenneth Raffenetti's avatar
      portals4: revert [722d85a4] and [d459c025] · 2f97f429
      Kenneth Raffenetti authored
      The 2 commits being reverted introduced a "safe" PtlMEAppend function
      that would call MPID_nem_ptl_poll to process some events in case there
      was no space to append the match list entry. However the poll function
      is not reentrant safe, which could lead to ordering problems.
      
      The increased list entry limit from [c6c0d6f6
      
      ] should prevent PTL_NO_SPACE
      errors from happening, except in the extreme case. If we still find we are
      hitting this error, a proper fix can be done in the Rportals layer.
      Signed-off-by: default avatarAntonio J. Pena <apenya@mcs.anl.gov>
      2f97f429
  5. 19 Nov, 2014 1 commit
  6. 14 Nov, 2014 1 commit
  7. 13 Nov, 2014 1 commit
  8. 12 Nov, 2014 4 commits
  9. 05 Nov, 2014 4 commits
  10. 04 Nov, 2014 1 commit
  11. 03 Nov, 2014 1 commit
    • Pavan Balaji's avatar
      Initial draft of flow-control in the portals4 netmod. · f4253c38
      Pavan Balaji authored
      
      
      Portals4 by itself does not provide any flow-control.  This needs to
      be managed by an upper-layer, such as MPICH.  Before this patch we
      were relying on a bunch of unexpected buffers that were posted to the
      portals library to manage unexpected messages.  However, since portals
      asynchronously pulls out messages from the network, if the application
      is delayed, it might result in the unexpected buffers being filled out
      and the portal disabled.  This would cause MPICH to abort.
      
      In this patch, we implement an initial version of flow-control that
      allows us to reenable the portal when it gets disabled.  All this is
      done in the context of the "rportals" wrappers that are implemented in
      the rptl.* files.  We create an extra control portal that is only used
      by rportals.  When the primary data portal gets disabled, the target
      sends PAUSE messages to all other processes.  Once each process
      confirms that it has no outstanding packets on the wire (i.e., all
      packets have either been ACKed or NACKed), it sends a PAUSE-ACK
      message.  When the target receives PAUSE-ACK messages from all
      processes (thus confirming that the network traffic to itself has been
      quiesced), it reenables the portal and sends an UNPAUSE message to all
      processes.
      
      This patch still does not deal with origin-side resource exhaustion.
      This can happen, for example, if we run out of space on the event
      queue on the origin side.
      Signed-off-by: Kenneth Raffenetti's avatarKen Raffenetti <raffenet@mcs.anl.gov>
      f4253c38
  12. 27 Aug, 2014 1 commit
  13. 07 Aug, 2014 2 commits
  14. 29 Oct, 2013 1 commit
  15. 17 Dec, 2012 1 commit
  16. 05 Nov, 2012 1 commit
  17. 26 Oct, 2012 1 commit
  18. 12 Oct, 2012 1 commit
  19. 10 Oct, 2012 1 commit
  20. 03 Oct, 2012 1 commit
  21. 11 Sep, 2012 1 commit
  22. 07 Sep, 2012 1 commit
  23. 29 Aug, 2012 1 commit
  24. 30 Jul, 2012 1 commit