Messages in this thread | | | Subject | Re: scheduler ignores need_resched flag in 2.2.x and 2.3.x? | Date | Tue, 21 Mar 2000 12:33:25 +0000 (GMT) | From | Alan Cox <> |
| |
> 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?
A process wake from interrupt state - eg a network event. Its not actually that uncommon. The window is small however so it isnt likely to get hit much.
- 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/
| |