> If the only two tasks in the system that wants the kernel lock are the
> wakenup task and the current-running task, then rescheduling the wakenup
> task in _place_ of the current task will work _fine_. There _won't_ be any
> contention of the lock simply because the current task will go offline
> waiting the next schedule sleeping in the _run_queue.
why are you assuming that just because a task wakes another task up it
goes to sleep immediately?? In a large amount of cases thats not true.
(bw_tcp is just one example)
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/