6 ms·
It's all about better L3 utilization. Cilk is good for using L1 and L2, i.e. caches that are core-local, and suboptimal for using L3, i.e. caches that are share
by leiroigh 7y ago
It's all about better L3 utilization. Cilk is good for using L1 and L2, i.e. caches that are core-local, and suboptimal for using L3, i.e. caches that are shared between cores.
- gpderetta 7y agoCan you expand on this or point me to a paper discussing this?
- ddragon 7y agoIn the presentation posted here there was a paper citation that compared in terms of cache the model used (parallel depth first scheduling) over work stealing, but I didn't have time to read it yet. https://www.cs.cmu.edu/%7Echensm/papers/ConstructiveCacheSharing_spaa07.pdf https://www.cs.cmu.edu/%7Echensm/papers/ConstructiveCacheSha...
- gpderetta 7y agoCan't manage to download the file though my flimsy mobile connection, but I'm starting to understand the difference.