On Saturday 14 October 2006 18:40, Open Source wrote: > I'm not so sure about that. Once the interrupt is finished being > serviced, the scheduler should immediately wake up > and service any blocked processes rather than sitting > idle for one CONFIG_HZ period (4 ms when CONFIG_HZ=250). > At least that's my intuition.
Think about it... If _each_ interrupt would trigger the scheduler, you can bring the whole system down with a single fast-period interrupt in the system. The scheduler is triggered by the timer interrupt or if a process waits. regards Wolfgang -- Das Leben kann nur rückwärts verstanden, muß aber vorwärts gelebt werden. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
