Why does Perf c2c display cachline contention for read-only variables?
I am running perf c2c
for a multi-threaded example (a threadpool that calculates a matrix multiplication in a work-stealing manner) and obtain curious results (cacheline contention for const-variables and few contentions for write-to variables at addresses I don’t understand.) The threads share two non-const variables: