-
Notifications
You must be signed in to change notification settings - Fork 28
Use Collective builder for benchmarks #302
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
base: sycl-develop
Are you sure you want to change the base?
Use Collective builder for benchmarks #302
Conversation
c7c4f8c
to
bf21e0f
Compare
}; | ||
|
||
template <> | ||
struct SubgroupTilingMap<Shape<_256,_256,_32>, cutlass::layout::RowMajor, cutlass::layout::RowMajor> { |
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.
Do you need those specializations just to match what was previously in benchmarks?
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.
No, my goal is make it more easily maintainable. If someone wants to tune one case then they can just add a specialization and move on.
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.
The benchmarks should be matched by the default case
…ilder_for_benchmarks
…ilder_for_benchmarks
…ilder_for_benchmarks
9ba2fcb
to
ed88809
Compare
Uses the collective builders for benchmarks.
Also updates the collective builder to handle all the current benchmarks. I've gone for a two pronged approached where CTA tiles and matrix layouts can be mapped directly to a copy atom and subgroup layout, but there is also a fallback heuristic . The fallback is based on what the benchmarks were previously targetting and could probably be simplified and made more robust.