ZMC2019 commited on
Commit
00a0f36
·
verified ·
1 Parent(s): ec51e7b

Reorganise: group 313 tasks into 17 families under tasks/, generators under tools/

Browse files
tasks/distributed-multi-gpu/dist-allgather-gemm/instruction.md CHANGED
@@ -71,6 +71,17 @@ cat /logs/verifier/details.json # correct / speedup / tflops
71
 
72
  Get `ag_gemm` **correct** first (match the torch reference), then optimize the overlap for TFLOP/s.
73
 
 
 
 
 
 
 
 
 
 
 
 
74
  ## Constraints
75
 
76
  - **Offline.** pypi / github / huggingface are firewalled — you cannot fetch the original kernel. Build the
 
71
 
72
  Get `ag_gemm` **correct** first (match the torch reference), then optimize the overlap for TFLOP/s.
73
 
74
+ ## Know your hardware — do not assume it
75
+
76
+ The exact GPU is deliberately not stated. Query it at run time with `torch.cuda.get_device_properties(0)`:
77
+ `.multi_processor_count` (size any persistent grid from this, never a constant),
78
+ `.shared_memory_per_block_optin`, register and thread limits, and the compute capability. `nvidia-smi --query-gpu=name,memory.total,clocks.max.sm --format=csv`
79
+ gives clocks, and `ncu` reports achieved occupancy and bandwidth directly.
80
+
81
+ Measure achieved HBM bandwidth with a large stream-copy rather than trusting a datasheet figure. Do not
82
+ hardcode an SM count, a tile size derived from one, or a peak FLOP/bandwidth constant — the same
83
+ submission is graded on whatever device it lands on.
84
+
85
  ## Constraints
86
 
87
  - **Offline.** pypi / github / huggingface are firewalled — you cannot fetch the original kernel. Build the
tasks/distributed-multi-gpu/dist-tp-fused-kernels/instruction.md CHANGED
@@ -62,6 +62,17 @@ cat /logs/verifier/details.json # per-kernel TFLOP/s + correctness
62
  Get one kernel correct end-to-end first, then optimize its overlap, then bring up the others. Correctness on
63
  all three is required before you score anything.
64
 
 
 
 
 
 
 
 
 
 
 
 
65
  ## Constraints
66
 
67
  - **Offline.** pypi / github / huggingface are firewalled. torch + `triton_dist` + NVSHMEM are pre-installed.
 
62
  Get one kernel correct end-to-end first, then optimize its overlap, then bring up the others. Correctness on
63
  all three is required before you score anything.
64
 
65
+ ## Know your hardware — do not assume it
66
+
67
+ The exact GPU is deliberately not stated. Query it at run time with `torch.cuda.get_device_properties(0)`:
68
+ `.multi_processor_count` (size any persistent grid from this, never a constant),
69
+ `.shared_memory_per_block_optin`, register and thread limits, and the compute capability. `nvidia-smi --query-gpu=name,memory.total,clocks.max.sm --format=csv`
70
+ gives clocks, and `ncu` reports achieved occupancy and bandwidth directly.
71
+
72
+ Measure achieved HBM bandwidth with a large stream-copy rather than trusting a datasheet figure. Do not
73
+ hardcode an SM count, a tile size derived from one, or a peak FLOP/bandwidth constant — the same
74
+ submission is graded on whatever device it lands on.
75
+
76
  ## Constraints
77
 
78
  - **Offline.** pypi / github / huggingface are firewalled. torch + `triton_dist` + NVSHMEM are pre-installed.