Skip to contentSkip to conversation

Externalize SLIT table

DISCUSSION Jack Steiner 1 participant 1 message Nov 18, 2004

lore
Share & tools
lore
#0 lore raw

(Resend of mail sent Nov 10, 2004 - as far as I can tell, it went nowhere)

Quoted 13 lines · Mark Goodwin
Quoted 10 lines · Matthew Dobson
Quoted 5 lines · Mark Goodwin

Once again however, it depends on the definition of distance. For nodes, we've established it's the ACPI SLIT (relative distance to memory). For cpus, should it be distance to memory? Distance to cache? Registers? Or what?

That's the real issue. We need to agree upon a meaningful definition of CPU-to-CPU "distance". As Jesse mentioned in a follow-up, we can all agree on what Node-to-Node "distance" means, but there doesn't appear to be much consensus on what CPU "distance" means.

Quoted 6 lines

How about we define cpu-distance to be "relative distance to the lowest level cache on another CPU". On a system that has nodes with multiple sockets (each supporting multiple cores or HT "CPUs" sharing some level of cache), when the scheduler needs to migrate a task it would first choose a CPU sharing the same cache, then a CPU on the same node, then an off-node CPU (i.e. falling back to node distance).

I think I like your definition better than the one I originally proposed (cpu distance was distance between the local memories of the cpus).

But how do we determine the distance between the caches.

Quoted 6 lines

Of course, I have no idea if that's anything like an optimal or desirable task migration policy. Probably depends on cache-trashiness of the task being migrated.

-- Mark

Signature · 4 lines
Thanks

Jack Steiner ([email protected])          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.