Messages in this thread |  | | From | kuznet@ms2 ... | Subject | Re: [patch] NE2000 | Date | Wed, 8 Nov 2000 19:45:26 +0300 (MSK) |
| |
Hello!
> > In any case, Andrew, where is the race, when we enter in sleeping state? > > Wakeup is not lost, it is just not required when we are not going > > to schedule and force task to running state. > > set_current_state(TASK_INTERRUPTIBLE); > add_wait_queue(...); > /* window here */ > set_current_state(TASK_INTERRUPTIBLE); > schedule(); > > If there's a wakeup by another CPU (or this CPU in an interrupt) in > that window, current->state will get switched to TASK_RUNNING. > > Then it's immediately overwritten and we go to sleep. Lost wakeup.
Look into code yet. It looks sort of different. Again:
> > Wakeup is not lost, it is just not required when we are not going > > to schedule and force task to running state.
So that it is right not depening on anything.
Alexey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |