<div dir="ltr">One that I know is through proc interface where the interrupt info is lodged in a file in /proc and the user code keeps polling on this file. Exact use of this is to be looked for. <br><br><br><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, May 14, 2013 at 3:24 PM, Gergely Buday <span dir="ltr"><<a href="mailto:gbuday@gmail.com" target="_blank">gbuday@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Prabhu nath wrote:<br>
<br>
> But if the device has to generate an interrupt on the reception of the data<br>
> then it is best for the driver code to be in the kernel space waiting for<br>
> the data, rather than in the user space because there is no efficient<br>
> mechanism till now for the control to be transferred to the waiting user<br>
> space code on the reception of the interrupt.<br>
<br>
</div>What are the curently available mechanisms for an interrupt to<br>
propagate into user space?<br>
<br>
Is there one that affects the scheduler?<br>
<span class="HOEnZb"><font color="#888888"><br>
- Gergely<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>Prabhunath G<br>Linux Trainer<br>Bangalore<br>
</div></div>