Re: user space device drivers

[Prabhu nath <gprabhunath@xxxxxxxxx>]

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.

On Tue, May 14, 2013 at 3:24 PM, Gergely Buday <gbuday@xxxxxxxxx> wrote:

Prabhu nath wrote:

> But if the device has to generate an interrupt on the reception of the data
> then it is best for the driver code to be in the kernel space waiting for
> the data, rather than in the user space because there is no efficient
> mechanism till now for the control to be transferred to the waiting user
> space code on the reception of the interrupt.

What are the curently available mechanisms for an interrupt to
propagate into user space?

Is there one that affects the scheduler?

- Gergely

--
Regards,
Prabhunath G
Linux Trainer
Bangalore

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies