Re: scheduler ignores need_resched flag in 2.2.x and 2.3.x?

From: Jamie Lokier (lk@tantalophile.demon.co.uk)
Date: Tue Mar 21 2000 - 11:03:00 EST


yodaiken@fsmlabs.com wrote:
> As far as I can tell,
> only place need_resched is set is in the scheduler and the sched idle loop.
> This is what makes Ingo's latency patch less dangerous: need_resched is hard
> to set. Your scenario requires that an interrupt routine, interrupting
> kernel mode, set needs_resched. Where does this happen?

Whenever an interrupt wakes up a process. Alan says it's uncommon, but
it depends what devices you're using. Some device drivers do it for all
interrupts, if a process is waiting for some information from the device.

-- Jamie

-
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/



This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:33 EST