Skip to content

Commit 5913391

Browse files
authored
Include missing run rules in LICENSE document
The LICENSE contained a defunct link to run rules. This commit includes the text directly in the LICENSE file.
1 parent e1fffc0 commit 5913391

File tree

1 file changed

+18
-3
lines changed

1 file changed

+18
-3
lines changed

LICENSE

+18-3
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,7 @@
1414
* with the following limitations:
1515
* 3a. In order to be referred to as "BabelStream benchmark results",
1616
* published results must be in conformance to the BabelStream
17-
* Run Rules published at
18-
* http://github.com/UoB-HPC/BabelStream/wiki/Run-Rules
19-
* and incorporated herein by reference.
17+
* Run Rules incorporated herein by reference.
2018
* The copyright holders retain the
2119
* right to determine conformity with the Run Rules.
2220
* 3b. Results based on modified source code or on runs not in
@@ -33,3 +31,20 @@
3331
* program constitutes acceptance of these licensing restrictions.
3432
* 5. Absolutely no warranty is expressed or implied.
3533
*———————————————————————————————————-------------------------------------------
34+
* Run Rules:
35+
*
36+
* In order to generate a valid BabelStream result measuring
37+
* *main memory bandwidth*, you should obey the following rules:
38+
*
39+
* 1. The array size must be large enough that increasing the array size does not
40+
* drastically change the reported bandwidth. If you satisfy this you will no
41+
* longer be affected by any cache effects.
42+
*
43+
* 2. Each kernel should take a few milliseconds. The resolution of the host timer
44+
* is probably in milliseconds so each kernel execution should be longer than the
45+
* timer resolution. Increase the array size if the kernels are too fast. You are
46+
* unlikely to break this rule if you follow rule 1.
47+
*
48+
* If you see a single BabelStream result, expect this to be the largest bandwidth
49+
* reported by the benchmark unless stated otherwise.
50+
*———————————————————————————————————-------------------------------------------

0 commit comments

Comments
 (0)