[PR #28] [CLOSED] Comment more clear, memory consistency model is normal memory model #211

Closed
opened 2026-10-26 21:14:54 +00:00 by bsakaguchi · 0 comments
Owner

📋 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)

  • a2e0d68 Merge pull request #2 from deepseek-ai/main
  • 92521df comment 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.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/DeepGEMM/pull/28 **Author:** [@A-transformer](https://github.com/A-transformer) **Created:** 2/27/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `comment_more_clear` --- ### 📝 Commits (2) - [`a2e0d68`](https://github.com/deepseek-ai/DeepGEMM/commit/a2e0d68eed35c9dcf78ce07d1a7576bd006ff17e) Merge pull request #2 from deepseek-ai/main - [`92521df`](https://github.com/deepseek-ai/DeepGEMM/commit/92521df34d7fd3e48d78ef075e306a2aa556b80c) comment more clear about Memory Consistency and Barrier Visibility ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `deep_gemm/include/deep_gemm/fp8_gemm.cuh` (+1 -1) </details> ### 📄 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 21:14:54 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepGEMM#211
No description provided.