From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.linuxppc.org, jsun@mvista.com
Subject: Re: [ANN] IRQ Latency tool 0.1.3 release.
Date: Tue, 25 Jul 2000 19:29:51 +0100 [thread overview]
Message-ID: <200007251835.TAA17680@hyperion.valhalla.net> (raw)
On Tue, Jul 25, 2000, Geert Uytterhoeven wrote:
> On Mon, 24 Jul 2000, Iain Sandoe wrote:
[...]
>> I still haven't found the "hard-block" that is effecting the overall audio
>> latency performance... ah well, back to the drawing board...
>
> Do you have IDE? The IDE driver turned out to be the major interrupt messing
> problem on m68k, since it can disable interrupts for quite a while.
I do, but the audio latency test (which is what promoted this interest in
doing the IRQ measurement) doesn't stress the IDE (I only have a CDROM on
the IDE bus). All the disk activity is via the AppleSCSI card.
However, I would like others with different configurations to try out the
test(s)... it's not much use if acceptable performance sound only happens on
*my* machine :-)
It's also true that all the 'little' IRQ blocks do add up - as I said when
my system is stressed up to 5% of the total elapsed time can be blocked... a
good motivation for driver writers to tune things methinks...
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-25 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 18:29 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-26 18:42 [ANN] IRQ Latency tool 0.1.3 release Iain Sandoe
2000-07-25 21:53 Iain Sandoe
2000-07-24 22:44 Iain Sandoe
2000-07-25 12:15 ` Geert Uytterhoeven
2000-07-25 18:23 ` Jun Sun
2000-07-25 21:39 ` Benjamin Herrenschmidt
2000-07-26 11:54 ` Geert Uytterhoeven
2000-07-28 10:13 ` Takashi Oe
2000-07-28 14:51 ` Geert Uytterhoeven
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=200007251835.TAA17680@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=geert@linux-m68k.org \
--cc=jsun@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.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.