Improve README clarity for global vs shared memory GUPS tests #61
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
- Add clear introduction explaining the two memory modes - Separate build instructions for static vs dynamic shared memory - Provide explicit examples for running each test type - Clarify performance implications of different shared memory allocations - Add performance considerations section Based on feedback from issue NVIDIA-developer-blog#56 discussion
|
I'll check the changes in the next few days and comment on them. |
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.
Summary
This PR improves the GUPS benchmark README documentation to more clearly distinguish between global memory and shared memory test modes, as well as static vs dynamic shared memory allocation methods, based on the discussion in issue #56.
Changes
Context
Based on feedback from @rkarim2 in issue #56, where it was noted that:
-s 0(maximum static allocation) vs-s n(dynamic allocation)Related Issues
Addresses documentation clarity issues discussed in #56
cc @rkarim2