| ... | ... | @@ -26,6 +26,8 @@ If you use only the 4 basic calls, those are the rules: |
|
|
|
* Call `LIKWID_MARKER_CLOSE` only once in your application. Recommendation is the end of the `main` routine of your code. There is **NO** guard if you call it multiple times and will overwrite the output file, skewing up results if you measure between two calls to `LIKWID_MARKER_CLOSE`, so don't do it.
|
|
|
|
* `LIKWID_MARKER_START(str)` and `LIKWID_MARKER_STOP(str)` should be called once per application thread. There is some logic inside if it is called not by all application threads, but there might be problems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* [My code region is quite short](https://github.com/RRZE-HPC/likwid/wiki/LikwidMarkerAPIPitfalls#my-code-region-is-quite-short)
|
|
|
|
* [The measured times for multiple threads vary although all perform the same operation](https://github.com/RRZE-HPC/likwid/wiki/LikwidMarkerAPIPitfalls#the-measured-times-for-multiple-threads-vary-although-all-perform-the-same-operation)
|
|
|
|
* [What about `LIKWID_MARKER_THREADINIT`?](https://github.com/RRZE-HPC/likwid/wiki/LikwidMarkerAPIPitfalls#what-about-likwid_marker_threadinit)
|
| ... | ... | |
