common/ompio: implement pipelined read and write operation #11185
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
implement pipelined file_write and file_read operations. This code is being used if a bounce buffer is required,e.g. when using device memory or a non-native data representation. The new code shows significant performance improvements for reading/writing device buffers compared to the previous code version, and reduces the memory footprint of the library by allocating smaller temporary buffers. The current code is only dealing with blocking file_read/write operations, non-blocking operations will follow in a second step. Signed-off-by: Edgar Gabriel <[email protected]> (cherry picked from commit c50ffa7)
bosilca
approved these changes
Dec 9, 2022
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.
implement pipelined file_write and file_read operations. This code is being used if a bounce buffer is required,e.g. when using device memory or a non-native data representation. The new code shows significant performance improvements for reading/writing device buffers compared to the previous code version, and reduces the memory footprint of the library by allocating smaller temporary buffers.
The current code is only dealing with blocking file_read/write operations, non-blocking operations will follow in a second step.
Signed-off-by: Edgar Gabriel [email protected]
(cherry picked from commit c50ffa7)