Skip to content

Commit

Permalink
Include missing run rules in LICENSE document
Browse files Browse the repository at this point in the history
The LICENSE contained a defunct link to run rules. This commit includes the text directly in the LICENSE file.
  • Loading branch information
tomdeakin authored Aug 28, 2024
1 parent e1fffc0 commit 5913391
Showing 1 changed file with 18 additions and 3 deletions.
21 changes: 18 additions & 3 deletions LICENSE
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,7 @@
* with the following limitations:
* 3a. In order to be referred to as "BabelStream benchmark results",
* published results must be in conformance to the BabelStream
* Run Rules published at
* http://github.com/UoB-HPC/BabelStream/wiki/Run-Rules
* and incorporated herein by reference.
* Run Rules incorporated herein by reference.
* The copyright holders retain the
* right to determine conformity with the Run Rules.
* 3b. Results based on modified source code or on runs not in
Expand All @@ -33,3 +31,20 @@
* program constitutes acceptance of these licensing restrictions.
* 5. Absolutely no warranty is expressed or implied.
*———————————————————————————————————-------------------------------------------
* Run Rules:
*
* In order to generate a valid BabelStream result measuring
* *main memory bandwidth*, you should obey the following rules:
*
* 1. The array size must be large enough that increasing the array size does not
* drastically change the reported bandwidth. If you satisfy this you will no
* longer be affected by any cache effects.
*
* 2. Each kernel should take a few milliseconds. The resolution of the host timer
* is probably in milliseconds so each kernel execution should be longer than the
* timer resolution. Increase the array size if the kernels are too fast. You are
* unlikely to break this rule if you follow rule 1.
*
* If you see a single BabelStream result, expect this to be the largest bandwidth
* reported by the benchmark unless stated otherwise.
*———————————————————————————————————-------------------------------------------

0 comments on commit 5913391

Please sign in to comment.