60Hz is nothing. Every modem does much more. It's definitely not
the interrupt latency. Better look at your driver. May be, it's
not waking up the reader (or at the wrong place).
> Note, it's not enough to service interrupt within 64msec, I also need to
> transfer the data into the application that is reading from the driver.
> The total rate is about 6Mb/sec for the least degree of compression.
That may be your problem. Linux is not a real-time OS. Latency in
user space is undefined. And if there are two task who want to run,
CPU time is spread between them (100Hz resolution).
Are you really sure, that the driver is dropping frames (lost ints)
and not the user space app?
Your could try to play with task priorities or scheduling policies
(man 1 nice, man 2 sched_setscheduler).
Ciao, ET.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/