[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[rtl] Re: low-latency benchmarks: excellent results of RTC clock + SIGIOnotification, audio-latency now down to 2.1ms!
- To: Benno Senoner <sbenno@gardena.net>
- Subject: [rtl] Re: low-latency benchmarks: excellent results of RTC clock + SIGIOnotification, audio-latency now down to 2.1ms!
- From: mingo@chiara.csoma.elte.hu
- Date: Sat, 11 Sep 1999 17:46:01 +0200 (CEST)
- cc: Paul Barton-Davis <pbd@op.net>, sct@redhat.com, est@hyperreal.org, andrea@suse.de, rtl@rtlinux.cs.nmt.edu, alsa-devel@alsa-project.org, David Olofson <audiality@swipnet.se>, yodaiken@fsmlabs.com, linux-kernel@vger.rutgers.edu, LAD Mail <linux-audio-dev@ginette.musique.umontreal.ca>, Roger Larsson <nra02596@norran.net>, linux-sound@vger.rutgers.edu
- In-Reply-To: <99091119242901.00756@linuxhost.localdomain>
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
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.cs.nmt.edu OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.cs.nmt.edu
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/