lkml.org 
[lkml]   [2002]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectAW: interrupt latency
Date
Hello again,

> Alan Cox [mailto:alan@lxorguk.ukuu.org.uk] wrote:
>
> I would expect port 0x378 on any modern PC to be on the X-bus
> not on ISA

Right, so it is fast enough for a quick test.


Actually I don't know where this thread has lead us. Was it really me who
typed the reference line? Anyhow. :->


When I was talking about interrupt latency, I ment this:

I do a hardware interrupt, use it as trigger on an oscilloscope, then
measure how long it takes until the printer port showbit shows up. (Ha! An
oscilloscope is fine for timing measurements!) The printer port is handled
first in the irq_function of my driver. That kind of "latency" I was talking
about. The jitter I get (because of NMI functions and more) I can guess by
changing the persistance of the oscilloscope.

And to those who think that the printer port might be to slow for that kind
of measurement, I did the same with a showbit I set on a PCI device (a PLD I
know the inside). That one is nanoseconds fast, so no relevant delay.

Okay, the kernel takes at least 8 microseconds time to "tell" the kernel
driver function that an interrupt is there. So my question still is: How
should I trace thru the kernel source after a hardware interrupt is there?

(I am running a Pentium-like ETX with 266 MHz CPU clock. Single CPU.)

But thanks for all helps, hints and interesting discusses!


Siegfried Wessler.

BTW: You can get down to 1ms jiffies without RT Linux easily ;-)
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.023 / U:2.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site