On Wed, 2012-05-09 at 23:18 +0000, Grant Edwards wrote: > I eventually figured out that my increased interrupt latency is due to > my ISR being run in a kernel thread instead of as a real ISR. Adding > the IRQF_NODELAY flag gets me the same average latency I had without > the RT patch. [It looks like that flag has a different name in 2.6.39 > and later?] Note, adding a IRQF_NODELAY is very dangerous. To keep the kernel fully preemptible (well mostly), spin-locks have been converted into mutexes. If the irq handler has one of these spinlocks that have been converted, it may schedule in the interrupt handler and crash the kernel. You can not schedule in interrupt context, which is why the RT kernel makes the interrupt handlers into threads. Also note, you may get better response if you up the interrupt thread's priority. Up it to 98, and you should see much better responses. Now I don't think you will make the 20us under load, but you won't do that in the non-RT patch either. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
