Messages in this thread | | | Date | Thu, 13 Apr 2006 08:42:41 +0200 | From | Burkhard Schölpen <> | Subject | Reduce IRQ latency or revise hardware? |
| |
Hello,
I have a question concerning IRQ latency. In this context I mean the time from an irq being triggered by some hardware until the interrupt service routine of my driver is called, so particularly I'm not concerned about some scheduling latency. I'm dealing with some custom hardware which has got hard realtime requirements (for now). Because the standard linux kernel cannot satisfy this requirement I wonder in which direction I should go ahead:
1. Is it somehow possible to fulfill the realtime requirements of the hardware by e.g. a realtime kernel patch or some kernel configuration fine tuning (at the moment I need a maximum hardware latency of about 100 microseconds)? 2. Or is it better to work on the hardware design (it's an FPGA on a PCI-board), so it can deal with higher latencies? Is the requirement of a maximum hardware IRQ latency to high in general?
Again I would like to underline that the main task is to get the interrupt handler invoked early enough, so I can get data out of a hardware FIFO. If this FIFO produces overflows, I get into big trouble, because the following data stream will be corrupted and the hardware must be reset. The programmer of the FPGA says that the buffer size is already at the maximum.
I use an ASUS P5LD2 motherboard with a Pentium-D dualcore-processor and Debian stable (kernel 2.6.15). I would be very grateful for some hints.
Kind regards Burkhard Schölpen _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |