> No. The migration_cost is an empirical runtime calculation that estimates the > relative cost of migrating a task within each level of sched domain. And even > that is sometimes grossly inaccurate because only two arbitrary CPUs are > chosen for this calculation within one sched domain at each level, thus > assuming that the migration_cost is the same between any and all two CPUs in > that sched domain, and that all the sched domains for a given level exhibit > equivalent migration_cost behavior. Sounds like this code needs to see if there is a SLIT table, and if there is use it to decide which cpus to use, rather than picking arbitrarily. -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
|