All of lore.kernel.org
 help / color / mirror / Atom feed
* interrupt latency/700microsecs
@ 2002-05-27 16:30 Muthal Sangam
  2002-05-27 16:43 ` William Lee Irwin III
  2002-05-27 18:53 ` Alan Cox
  0 siblings, 2 replies; 3+ messages in thread
From: Muthal Sangam @ 2002-05-27 16:30 UTC (permalink / raw)
  To: linux-kernel


On kernel 2.4.7, AMDK6 @ 450MHz processor, is it possible to get latency
fluctuations of upto 700microsecs for running the timer interrupt, due to
interrupts being disabled ?

I am using the time stamp counter and reading it at the start of the timer
interrupt and measuring the cycles elapsed between two inovocations of it.
The number of cycles elapsed is ~4500225, but sometimes it increases to as
high as 4848032. Can i conclude that this difference is due to interrupts
being disabled in critical sections ? ( I think i am making some mistake :-)

- sangam


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: interrupt latency/700microsecs
  2002-05-27 16:30 interrupt latency/700microsecs Muthal Sangam
@ 2002-05-27 16:43 ` William Lee Irwin III
  2002-05-27 18:53 ` Alan Cox
  1 sibling, 0 replies; 3+ messages in thread
From: William Lee Irwin III @ 2002-05-27 16:43 UTC (permalink / raw)
  To: Muthal Sangam; +Cc: linux-kernel

On Mon, May 27, 2002 at 08:30:06PM +0400, Muthal Sangam wrote:
> On kernel 2.4.7, AMDK6 @ 450MHz processor, is it possible to get latency
> fluctuations of upto 700microsecs for running the timer interrupt, due to
> interrupts being disabled ?
> I am using the time stamp counter and reading it at the start of the timer
> interrupt and measuring the cycles elapsed between two inovocations of it.
> The number of cycles elapsed is ~4500225, but sometimes it increases to as
> high as 4848032. Can i conclude that this difference is due to interrupts
> being disabled in critical sections ? ( I think i am making some mistake :-)

IIRC there have been prior reports of excessive interrupt disablement
in 2.4.x, and also IIRC it was reported against a more recent kernel.
I think it was suspected there are bug(s) where some code is leaving
interrupts off and someone later unconditionally turns them back on.

Any chance you could upgrade to a more recent kernel and try to
reproduce there? There have been a number of critical bugfixes since 2.4.7
(and although none are particularly pertinent to this issue, people would
probably rather field bug reports for 2.4.19-pre* than 2.4.7).


Cheers,
Bill

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: interrupt latency/700microsecs
  2002-05-27 16:30 interrupt latency/700microsecs Muthal Sangam
  2002-05-27 16:43 ` William Lee Irwin III
@ 2002-05-27 18:53 ` Alan Cox
  1 sibling, 0 replies; 3+ messages in thread
From: Alan Cox @ 2002-05-27 18:53 UTC (permalink / raw)
  To: Muthal Sangam; +Cc: linux-kernel

On Mon, 2002-05-27 at 17:30, Muthal Sangam wrote:
> On kernel 2.4.7, AMDK6 @ 450MHz processor, is it possible to get latency
> fluctuations of upto 700microsecs for running the timer interrupt, due to
> interrupts being disabled ?
> 
> I am using the time stamp counter and reading it at the start of the timer
> interrupt and measuring the cycles elapsed between two inovocations of it.
> The number of cycles elapsed is ~4500225, but sometimes it increases to as
> high as 4848032. Can i conclude that this difference is due to interrupts
> being disabled in critical sections ? ( I think i am making some mistake :-)

In X with a matrox G200 I've observed processor stalls in excess of 1mS
so Im not actually much suprised.



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-05-27 17:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-27 16:30 interrupt latency/700microsecs Muthal Sangam
2002-05-27 16:43 ` William Lee Irwin III
2002-05-27 18:53 ` Alan Cox

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.