Summa overlap fix #33
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Used OpenMP tasking to drive two parallel progress in each SUMMA stage - one to drive the asynchronous broadcast with repeatative polling, second to drive the local spgemm on previously received data - Outdated function call to read triples files fixed in MultTiming
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes Issue# 32
Communication computation overlap is achieved in each SUMMA stage using asynchronous broadcast calls and OpenMP tasks. In each SUMMA stage, four asychronous broadcasts are called; then split the OpenMP threads into two tasks - one for continuous probing to progress communication while rest to drive the local-SpGEMM. MultiwayMerge is used when all SUMMA stages are finished as usual.