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

Understanding sync and arrive in FA3 Store Function #1401

Open
ziyuhuang123 opened this issue Dec 19, 2024 · 0 comments
Open

Understanding sync and arrive in FA3 Store Function #1401

ziyuhuang123 opened this issue Dec 19, 2024 · 0 comments

Comments

@ziyuhuang123
Copy link

Does anyone understand why the number of sync operations in the FA3 store function (

cutlass::arch::NamedBarrier::arrive(NumEpilogueThreads + cutlass::NumThreadsPerWarp,
) is 256+32 (within a single warp, with all threads arriving)? Why does the non-varlen case require arrive before sync, while the varlen case only needs sync without arrive?
28776ba74d6b485251b90479ca954da

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

No branches or pull requests

1 participant