[lkml]   [2003]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] 2.5 TASK_INTERRUPTIBLE preemption race
On Mon, 2003-04-14 at 18:27, Joe Korty wrote:

> I see. It is because the 'goto pick_next_task' skips the
> 'deactivate_task' call. Therefore the previous task remains on the
> run queue in spite of its TASK_UNINTERRUPTIBLE state. Clever!

Yep :)

We actually did away with it for a bit in mid 2.5... it turned out to
not be worth it. Its a little odd to use the flag like that, but its
quite simply and the results are good.

Means we can safely schedule anytime, no matter the state. There are
tons of other places where we would not want to sleep if it were not for

Robert Love

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:34    [W:0.052 / U:5.192 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site