From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Muthal Sangam <sangam@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: interrupt latency/700microsecs
Date: 27 May 2002 19:53:46 +0100 [thread overview]
Message-ID: <1022525626.11859.307.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <E17CNNm-000GQe-00@f11.mail.ru>
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.
prev parent reply other threads:[~2002-05-27 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 16:30 Muthal Sangam
2002-05-27 16:43 ` William Lee Irwin III
2002-05-27 18:53 ` Alan Cox [this message]
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=1022525626.11859.307.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®