From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: jsun@mvista.com
Subject: [ANN] IRQ Latency tool 0.1.3 release.
Date: Mon, 24 Jul 2000 23:44:04 +0100 [thread overview]
Message-ID: <200007242244.XAA21388@hyperion.valhalla.net> (raw)
Hi list...
Well, here is a tool that should allow identification of rogue IRQ blocks
(ints held off for a long time).
This is important to those of us trying to do audio on LinuxPPC - it would
be a great shame if we couldn't succeed where MacOS 9 already performs...
Many thanks to Jun Sun for the code that was the inspiration (and basis) of
this...
It is well-tested on my system but needs other input...
It needs some development input before it's going to work on Gemini/APUS/8xx
- because the code is too hairy to do without a system to test on (well for
me it is anyway :-)
Take a look, have a go, tell me what happens....
http://www.drfruitcake.com/linux/irq_blk.html
BTW: on my system ll_rw_blk.c gets up to 750 us quite often when the system
is loaded... this **IS** a potential problem for audio use.
log entry : 3 (16 history entries)
Peak Block Time : 430.0 us ( 7185) [ OK ]
startFilename : ll_rw_blk.c Line : 167
endFileName : ll_rw_blk.c Line : 179
I still haven't found the "hard-block" that is effecting the overall audio
latency performance... ah well, back to the drawing board...
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-24 22:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 22:44 Iain Sandoe [this message]
2000-07-25 12:15 ` [ANN] IRQ Latency tool 0.1.3 release 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
2000-07-29 0:47 ` [linux-fbdev] " James Simmons
-- strict thread matches above, loose matches on Subject: below --
2000-07-25 18:29 Iain Sandoe
2000-07-25 21:53 Iain Sandoe
2000-07-26 18:42 Iain Sandoe
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=200007242244.XAA21388@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).