When GPU work in one block depends on work in another, a block-level barrier cannot coordinate them. The kernel boundary—the point where one kernel returns and the next launch begins—is where all blocks are guaranteed to have finished; prior writes are visible in an ordinary same-stream launch sequence. section 11.4
Use the boundary to handle dependencies across blocks:
- Split dependent work into separate kernel launches rather than trying to make blocks wait for one another inside a kernel. section 11.4
- Do not confuse this with __syncthreads(), which synchronizes threads only within one block. section 11.4
Algorithms with cross-block dependencies
Multi-block scan, level-synchronous BFS, and wavefront dynamic programming rely on kernel boundaries to separate dependent stages. section 11.4
