RE: Interrupt Latencies
From: Schaefer Dr, Frank-Rene ()
Date: Thu Feb 24 2011 - 03:02:17 EST
In response to Thomas Gleixner:
> Interrupt latency depends on various factors:
> - Interrupt disabled code regions
Could you tell us how this could be detected or measured?
Is there a central place, where we could toggle a pin to
see when interrupts are enabled/disabled?
> - Concurrent interrupts and the ordering of handling
We are only considering the best times that we measure.
The only other interrupts are SATA and system timer, I guess.
> - Deep idle states
You mean 'suspend' or some type of CPU sleep. Could you elaborate?
We do not suspend. This should also only be the case for the
first chunk that is transmitted. But the latencies remain
over longer time spans.
> - Bus contention
Nothing else is running.
> - Cache misses
We cannot make any statements about that. But, we are **not**
working on huge data or code regions.
> > pin IN .-------------------------
> > ______________|
> > pin OUT .-----------
> > ____________________________|
> > |<- latency ->|
> How is that interrupt connected to the CPU/chipset?
The port is part of the chipset connected internally
> Which driver(s) is/are involved ?
> How is the pin OUT accessed from the driver?
we measured the delay and could find that it was in the range
of some nano seconds.
Frank Schäfer and Joachim Becker.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/