mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #28] [CLOSED] Comment more clear, memory consistency model is normal memory model #211
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/28
Author: @A-transformer
Created: 2/27/2025
Status: ❌ Closed
Base:
main← Head:comment_more_clear📝 Commits (2)
a2e0d68Merge pull request #2 from deepseek-ai/main92521dfcomment more clear about Memory Consistency and Barrier Visibility📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
deep_gemm/include/deep_gemm/fp8_gemm.cuh(+1 -1)📄 Description
Memory Consistency and Barrier Visibility: Both __syncthreads() and cute::cluster_sync() serve as synchronization points, ensuring that all threads reach the barrier before any proceed. This guarantees that all prior memory operations, including barrier initialization, are visible to all threads within the synchronization scope.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.