> I am not familiar with that. Does the migration_cost take the > SLIT node distances into consideration? migration_cost measures the actual node-node latency. It gets printed early in console output. Since I only have one-node boxes, I just see: migration_cost=10002 but I think on a multi-node box you'll get a string of numbers. Ah, but looking at the code, I think I was mistaken ... it seems to only know about distances between scheduler domains ... which may or may not match with all the node information. But it might still be worth looking at to see whether it can be used, or can be easily extended to be used. A measured value is often better than a static define that doesn't apply to all systems. -Tony - : send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|