On Jan 31, 2012, at 3:20 PM, Brice Goglin wrote:
> In 1.5.x, cache info doesn't matter as far as I know.
> In trunk, the affinity code has been reworked. I think you can bind
> process to caches there. Binding to L2 wouldn't work as expected (would
> bind to one core instead of 2). hwloc doesn't have instruction cache
> support so far, so wrong L1i info doesn't matter.
> I don't know if anybody in trunk uses shared cache size yet (for BTL SM
> tuning for instance).
That information is all correct.
For corporate legal information go to: