Clarify scan benchmarks

NVIDIA · Feb 6, 2025 · 5998318 · 5998318
1 parent 40737d6
commit 5998318
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/cub/benchmarks/bench/scan/exclusive/max.cu → ...benchmarks/bench/scan/exclusive/custom.cu b/cub/benchmarks/bench/scan/exclusive/max.cu → ...benchmarks/bench/scan/exclusive/custom.cu
@@ -25,6 +25,12 @@
  *
  ******************************************************************************/
 
+// This benchmark uses a custom operation, max_t, which is not known to CUB, so no operator specific optimizations and
+// tunings are performed.
+
+// Because CUB cannot detect this operator, we cannot add any tunings based on the results of this benchmark. Its main
+// use is to detect regressions.
+
 // %RANGE% TUNE_ITEMS ipt 7:24:1
 // %RANGE% TUNE_THREADS tpb 128:1024:32
 // %RANGE% TUNE_MAGIC_NS ns 0:2048:4

diff --git a/cub/benchmarks/bench/scan/exclusive/sum.cu b/cub/benchmarks/bench/scan/exclusive/sum.cu
@@ -25,6 +25,8 @@
  *
  ******************************************************************************/
 
+// Tuning parameters found for signed integer types apply equally for unsigned integer types
+
 #include <nvbench_helper.cuh>
 
 // %RANGE% TUNE_ITEMS ipt 7:24:1