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

[AMD] Remove tritonamdgpu-stream-pipeline #4845

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sjw36
Copy link
Contributor

@sjw36 sjw36 commented Oct 3, 2024

No description provided.

Copy link
Collaborator

@antiagainst antiagainst left a comment

Choose a reason for hiding this comment

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

Yay! Just one final nit.

else:
if options.num_stages == 0:
amd.passes.ttgpuir.add_stream_pipeline(pm)
num_stages = options.num_stages if options.num_stages != 0 else 2
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should also drop this too--it was meant to smooth transition. After v1 gone we need to respect what the user set--if it's 0 then we don't pipeline anymore.

Copy link
Collaborator

Choose a reason for hiding this comment

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

This will have a big influence on almost everyone. For now, all gemm-like kernels on AMD backend uses num_stages=0. Removing it will cause a significant perf regression.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah num_stages=0 just need to be fixed in all downstream users--we cannot be beholden to that.

Copy link
Collaborator

@antiagainst antiagainst left a comment

Choose a reason for hiding this comment

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

LGTM! Just blocking for now to still wait for sometime for stability of v2 before landing.

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

Successfully merging this pull request may close these issues.

3 participants