Hi Asutosh .. How r u doing ............ I hope below will clear .. or for more detail http://lwn.net/Articles/302043/ 1. threaded interrupt handlers Benifits: a) Reduce latency b) reduce locking between hard and soft part. 1. threaded interrupt handlers Benifits: a) Reduce latency b) reduce locking between hard and soft part. Threaded interrupt handlers reduce that work even further, so the top half would consist of a "quick check handler" that just ensures the interrupt is from the device; if so, it simply acknowledges the interrupt to the hardware and tells the kernel to wake the interrupt handler thread On Wed, Jan 25, 2012 at 10:15 AM, Asutosh Das <das.asutosh@xxxxxxxxx> wrote: > Hi > I have a query regarding the difference between request_irq and > request_threaded_irq. > I am aware that the thread_fn_handler may sleep, allocate memory, > acquire locks etc. > > What context does the thread fn passed to the request_threaded_irq run in ? > > TIA > > -- > ~/asd > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
