On Tue, 2006-01-10 at 17:59 -0600, Robert Hancock wrote:
> Most likely some driver is disabling interrupts for that period, which
> is really longer than it should be. However, if your card/driver require
> such tight interrupt latency to function correctly, that seems too
> fragile and may not be reliable. Some kind of ringbuffer arrangement
> would likely work better, so that the interrupt does not have to be
> serviced so soon.
>
You can easily tell if this is the case by applying these patches:
http://people.redhat.com/mingo/latency-tracing-patches/latency-tracing-patches-2.6.15-rc7.tar.gz
It says -rc7 but they apply cleanly and work with 2.6.15 final.
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
