On Wed, Jul 27, 2011 at 11:30:08AM -0700, Paul E. McKenney wrote:
> o Tasks awakening outside of migrate-disable regions will pick
> the CPU running the lowest-priority task, whether or not this
> task is in migrate-disable state. (At least I don't see
> anything in 3.0-rt3 that looks like a scheduling decision
> based on ->migrate_disable, perhaps due to blindness.)
I'm also confused here, seems we just disable migration for RT task.
migrate_disable()
{
...
if (p->sched_class->set_cpus_allowed)
p->sched_class->set_cpus_allowed(p, mask);
p->rt.nr_cpus_allowed = cpumask_weight(mask);
...
}
Shouldn't we also forbid migration on !RT task?
Thanks,
Yong
--
Only stand for myself
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
