[QST]What's the difference between: pipeline.producer_commit and pipeline.producer_get_barrier
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
What is your question?
In test/unit/pipeline/pipeline_tma_async_warp_specialized.cu, I see:
pipeline.producer_commit
And in cutlass/include/cutlass/gemm/collective/sm90_mma_tma_gmma_ss_warpspecialized.hpp, I see:
pipeline.producer_get_barrier
They locates at almost same place, so I guess they have same function. Why? Any difference? They are the same?(from source code I can not understand)
Thanks~
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the uses of pipeline.producer_commit in test/unit/pipeline/pipeline_tma_async_warp_specialized.cu and pipeline.producer_get_barrier in cutlass/include/cutlass/gemm/collective/sm90_mma_tma_gmma_ss_warpspecialized.hpp. Start by tracing the surrounding pipeline operations and source definitions; done means providing a clear explanation of their different behavior or confirming that they are equivalent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100