Chris Friesen writes: > Suppose I have a SCHED_FIFO task spinning on recvmsg() with MSG_DONTWAIT > set (and maybe doing other stuff if there are no messages). In this > case, schedule() would re-run the spinning task rather than running > ksoftirqd. This could prevent any incoming packets from actually being > sent up the stack until we get a real hardware interrupt--which could be > a whole jiffy if interrupt mitigation is enabled in the net device.
I suggest you ask Ingo Molnar about that. > (And maybe longer if NOHZ is enabled.) We still have a timer interrupt every jiffy when stuff is running; we only turn off the timer interrupts when idle. Paul. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
