-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CUDA] Allow dynamic shmem of size > 48K in runtime #11478
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -164,11 +164,22 @@ class CUDAWrappedFunc { | |
void operator()(TVMArgs args, TVMRetValue* rv, void** void_args) const { | ||
int device_id; | ||
CUDA_CALL(cudaGetDevice(&device_id)); | ||
ThreadWorkLoad wl = launch_param_config_.Extract(args); | ||
|
||
if (fcache_[device_id] == nullptr) { | ||
fcache_[device_id] = m_->GetFunc(device_id, func_name_); | ||
if (wl.dyn_shmem_size >= (48 << 10)) { | ||
// Assumption: dyn_shmem_size doesn't change across different invocations of | ||
// fcache_[device_id] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This assumption could be controversial, but this should be mostly ok in practice. To support a kernel which uses different big shmem sizes depending on input, we need to call |
||
CUresult result = cuFuncSetAttribute( | ||
fcache_[device_id], CU_FUNC_ATTRIBUTE_MAX_DYNAMIC_SHARED_SIZE_BYTES, wl.dyn_shmem_size); | ||
if (result != CUDA_SUCCESS) { | ||
LOG(FATAL) << "Failed to set the allowed dynamic shared memory size to " | ||
<< wl.dyn_shmem_size; | ||
} | ||
} | ||
} | ||
CUstream strm = static_cast<CUstream>(CUDAThreadEntry::ThreadLocal()->stream); | ||
ThreadWorkLoad wl = launch_param_config_.Extract(args); | ||
CUresult result = cuLaunchKernel(fcache_[device_id], wl.grid_dim(0), wl.grid_dim(1), | ||
wl.grid_dim(2), wl.block_dim(0), wl.block_dim(1), | ||
wl.block_dim(2), wl.dyn_shmem_size, strm, void_args, nullptr); | ||
|
This file contains 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 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.
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.
if dynamic memory is too large, will it pass
VerifyGPUCode
check?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.
Haven't tested but yeah, it seems
VerifyGPUCode
checks the static alloc size againstmax_shared_memory_per_block
, which would fail ifdyn_shmem_size >= (48 << 10)
tvm/src/tir/analysis/verify_gpu_code.cc
Lines 70 to 71 in 534205b
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 defer this issue later? I need this to demonstrate that a multi-stage pipeline with depth > 2 works on a semi-realistic cuda schedule.
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.
Yeah let's defer this particular issue