From: <mingo@chiara.csoma.elte.hu>
To: linux-sound@vger.kernel.org
Subject: Re: low-latency benchmarks: excellent results of RTC clock + SIGIO
Date: Sat, 11 Sep 1999 15:46:01 +0000 [thread overview]
Message-ID: <marc-linux-sound-93706522629904@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93706455029492@msgid-missing>
On Sat, 11 Sep 1999, Benno Senoner wrote:
> Seems that under high disk I/O load,
> (very seldom, about every 30-100secs) the process
> gets woken up one IRQ period later.
> Ideas why this happens.
this could be a lost RTC IRQ. If you are using 2048 Hz RTC interrupts, it
just needs a single 1msec IRQ delay to lose an RTC IRQ. Especially SCSI
disk interrupts are known to sometimes cause 1-2 millisecs IRQ delays.
But before jumping to conclusions, what exactly are the symptoms, what
does 'one IRQ period later' mean exactly?
-- mingo
next prev parent reply other threads:[~1999-09-11 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-11 15:42 low-latency benchmarks: excellent results of RTC clock + SIGIO notification, audio-latency now down Benno Senoner
1999-09-11 15:46 ` mingo [this message]
1999-09-11 16:12 ` low-latency benchmarks: excellent results of RTC clock + SIGIO notification, audio-latency now d Benno Senoner
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=marc-linux-sound-93706522629904@msgid-missing \
--to=mingo@chiara.csoma.elte.hu \
--cc=linux-sound@vger.kernel.org \
/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.