On Tue, 2014-07-22 at 15:30 +0400, Kirill Tkhai wrote: > Bad situation: > > double_lock_balance() drops busiest_rq lock. The busiest_rq is *busiest*, > and a lot of tasks and context switches there. We are dropping the lock > and waiting for it again. > > Let's just detach the task and once finally unlock it! > > Warning: this admits unlocked using of can_migrate_task(), > throttled_lb_pair(), > and task_hot(). I added comments about that. >
Wonder if we should also consider removing double_lock_balance usage from rt.c and deadline.c? Then those two schedulers will also not lock both the source and destination queues at the same time for load balancing. Tim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
