-
Notifications
You must be signed in to change notification settings - Fork 55
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
[WIP] Scheduling propagation through broadcast IDs #3763
base: main
Are you sure you want to change the base?
Conversation
PR Reviewer Guide 🔍(Review updated until commit bf6412e)Here are some key observations to aid the review process:
|
**Background** To avoid running Hopper matmul tests on Blackwell GPUs (there are unsupported ptx), `HopperBase` was changed from `Hopper & Newer` to `Hopper Only` at [#3754](https://github.com/NVIDIA/Fuser/pull/3754/files#diff-fb98e47b0b389ef77407ef12badf08c42718a0e81dfce9ac5a6eca06feaca1c4R616-R617) . **Changes in this PR** To still keep testing `TMA` on both Hopper and Blackwell GPUs, in this PR, the parent class of `TMATest` is changed from `HopperBase` to `TMABase`. `TMABase` allows running tests on `Hopper & Newer`
Just found some unintuitive traversal with the permissive BFS. For example, when there's a graph like: ``` a -> b, c (e.g., split) ``` When traversing from just `{b}`, the normal BFS won't allow any move since the backward traversal requires both `b` and `c`. The permissive BFS, on the other hand, allows to visit `a` since it allows traversal whenever there's at least one node already visited. That's all I had in mind when I added the permissive BFS, but it turned out that it also visits `c` as well. The first move is `b, c -> a` while allowing the missing `c`, and the second move is `a -> b, c` since `a` is now visited and `c` is not yet visited. This doesn't seem to make sense since the reason `a` is visited is because we take the backward traversal of the edge. That in turn allows the forward traversal doesn't seem to be the right thing to do. While I'm not aware of any particular impact due to this behavior, this PR prevents such traversal by checking if any of Val nodes is already marked as a previous node of an Expr node.
a8d3a41
to
34a57d5
Compare
…alc' into schedule_loop_domains_broadcast
Description
Changes walkthrough 📝
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
No description provided.