Messages in this thread |  | | Date | Thu, 8 May 2003 12:22:05 -0700 | From | Andrew Morton <> | Subject | Re: 2.5.69 Interrupt Latency |
| |
Paul Fulghum <paulkf@microgate.com> wrote: > > On Wed, 2003-05-07 at 17:28, Andrew Morton wrote: > > Paul Fulghum <paulkf@microgate.com> wrote: > > > > > > 2.5.69 > > > Latency 100-110usec (5x increase) > > > Spikes from 5-10 milliseconds > > > > > > If you can describe what drivers are in use, and what workload triggers the > > problem then it may be locatable by inspection. > > After inspecting both machines, there is no common > hardware other than the net device. Both machines > use the e100 driver. > > After removing the e100 driver altogether, > the increased latency and latency spikes persist. > > So it looks like this problem is not specific to a > particular hardware driver, but is a result of a > more fundemental, system wide change. > > I'm going to try your suggestion of doing a stack dump > when the driver encounters the large spikes in IRQ latency, > to determine if something is leaving interrupts disabled.
I wasn't very informative, alas.
> That will not address the fact that the minimum > latency has jumped from 20usec (2.4.20 - 2.5.68) to 100usec > (2.5.69). This may actually be two separate problems > introduced with 2.5.69
Can you pinpoint a kernel version at which it started to happen? - 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/
|  |