Skip to content
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

[CK][HIP] limit the range of several CK HIP kernels #2005

Merged
merged 1 commit into from
Mar 2, 2023
Merged

Conversation

carlushuang
Copy link
Contributor

This can partial fix #2004 by limiting several CK HIP kernel within the range of 2G

@junliume junliume changed the title limit the range of several CK HIP kernels [CK][HIP] limit the range of several CK HIP kernels Mar 1, 2023
Copy link
Collaborator

@junliume junliume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see series of PRs dated back from #243 and let's make sure this time we get all the CK kernels patched properly

@junliume junliume added this to the ROCm 5.5 milestone Mar 1, 2023
@junliume junliume merged commit ff88d3d into develop Mar 2, 2023
@atamazov
Copy link
Contributor

atamazov commented Mar 2, 2023

@carlushuang @junliume 🔴
This requires find-db update to avoid perf drops in cases when the best solution is of ImplicitGemm algorithm.
Please set https://github.com/ROCmSoftwarePlatform/MIOpen/labels/IMPACTS_FIND_DB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug][CK][Static Kernel][ConvHipImplicitGemmV4R1Fwd] Possible Overflow with Large Values of Channels
3 participants