You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that if we use it as __syncthreads, there's no need for arrive. bar.arrive is meant for use in WASP, isn't it? Although using a barrier for WASP feels odd... doesn't this forcibly require the producer and consumer to have the same participating threads?
In the FA3 store function, I observed the following process:
This sync is a NamedBarrier sync, but I noticed that no arrive operation is performed:
This reminds me of
__syncthreads
, which translates to PTX asbar.sync
and also doesn’t involve an explicitarrive
.This raises the question:
arrive
is unnecessary for such synchronization scenarios?However, I noticed that in other parts of FA3,
arrive
is used.Therefore, I’m curious:
arrive
is required?The text was updated successfully, but these errors were encountered: