mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #105] Some supplementary on ld.nc in PTX model and texture memory for pragmatic guess in README #94
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/DeepEP#94
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?
Originally created by @zsnoob on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/105
https://github.com/deepseek-ai/DeepEP/issues/21#issuecomment-2764894125
This comment refered that: 'nc encourages NVCC to do more optimizations.' I'm so curious about the hardware side of this architecture-specific characteristic beyond compiler optimization, so I did some summary from docs. Hope others who are also interested in this detail will find the information helpful and get some inspiration for own program design.
Though we disable the texture cache's allocation, the behavior how it process access requests may still occur.
To accelerate memory access, GPUs typically rely on coalescing. However, this optimization comes with certain constraints. The texture cache mechanism can be used to get around coalescing constraints. We have better performance when data access is out of coalesced constraints and have sufficient parallelism.
Reference:
https://docs.nvidia.com/cuda/parallel-thread-execution
https://docs.nvidia.com/cuda/cuda-c-best-practices-guide
https://docs.nvidia.com/gameworks/content/developertools/desktop/analysis/report/cudaexperiments/kernellevel/memorystatisticsglobal.htm