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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up and simplify
gpuDecideCompression
#13202Clean up and simplify
gpuDecideCompression
#13202Changes from 6 commits
678b371
2f1e493
2a63e92
6660143
02fd2a3
8da94ca
f30861b
df95f7b
0e541c0
618f070
4acb28f
2b18f54
aba6ef2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we write this kernel in a block-size agnostic way? Unlike
__syncthreads();
, using__syncwarp();
assumes thatblock_size == warp_size == 32
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That depends on how we would scale the parallelism with multiple warps. If any warps worked on a single
chunks
element, then, yes, we would need to syn all threads in the block. But, with multiple warps, IMO this kernel should actually have each warp would work on a separatechunks
element. In this case we don't need to synchronize different warps and__syncwarp
is still the right option.I understand that my change left this ambiguous as warp size is used interchangeably for block and warp size. I'll try to make this clearer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Modified the kernel to work with any number of warps in a block. The size can be adjusted via
constexpr
decide_compression_warps_in_block
. Used warp_size as well, so we should be magic number-free now :)