Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C codes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • codes
  • codes
  • Merge requests
  • !40

Merged
Created Sep 13, 2017 by Misbah Mubarak@mubarakOwner

Fixing early event triggers when using rendezvous protocol

  • Overview 0
  • Commits 5
  • Changes 3

With the simulated rendezvous protocol, the sender does a handshake first by sending a control message to the receiver. Once the control message arrives at the receiving end, it checks whether a matching receive has been posted or not. If not, it will wait until matching receive gets posted. If it finds a matching receive, an acknowledgement is sent to the sender to initiate the data transfer.

In the updated rendezvous protocol, the MPI_send/isend and recv behavior has been modified as follows

  • MPI_send does not complete until the actual data transfer has completed from the sender side. Similarly, MPI_isend does not mark the request as completed until the actual data has been sent.
  • MPI_recv does not complete until the actual data has arrived. Same way, MPI_irecv will not mark the request as completed until the data transfer has completed from the receiver side.
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: rend-fix