[AMD][Backend, Atomics] Remove old comment regarding buffer atomics #5523
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.
Overview
I spent a day investigating an old comment in the AMD backend regarding buffer atomics (specifically buffer atomic RMW) which suggested that buffer atomics perform better on MI-* series GPUs. The branch I worked on is available here for reference.
I think that (today, maybe this was different in the past) as far as I can tell the only benefit that buffer atomics (on their own) offer is the same hardware masking benefits that other buffer ops have (i.e., atomics out of bounds are dropped). This depends on how the buffer atomics are synchronized though, and this is where I'm less sure of whats correct:
With full barriers (identical performance to "normal" atomics):
With some assumptions specific to gfx942 (This can improve latency in bw-bound Split-K for some but not all shapes, it seems this is what CK does):
If there is interest, I can file a PR to add experimental support for buffer atomic RMW ops. The only major difference with my implementation is that I added support for CTA-scope (atomics in the AMD backend today only support agent scope as far as I can tell I think).
==================================================================
New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
[ x] I have run
pre-commit run --from-ref origin/main --to-ref HEAD
.Select one of the following.
/test
forlit
tests/unittest
for C++ tests/python/test
for end-to-end testsjust removing a comment
.Select one of the following.
lit
tests.lit
tests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)