All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Muthal Sangam <sangam@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: interrupt latency/700microsecs
Date: Mon, 27 May 2002 09:43:03 -0700	[thread overview]
Message-ID: <20020527164303.GP14918@holomorphy.com> (raw)
In-Reply-To: <E17CNNm-000GQe-00@f11.mail.ru>

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

  reply	other threads:[~2002-05-27 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 16:30 interrupt latency/700microsecs Muthal Sangam
2002-05-27 16:43 ` William Lee Irwin III [this message]
2002-05-27 18:53 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020527164303.GP14918@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sangam@mail.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.