From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: IRQ Blocking Test 0.1.3
Date: Fri, 28 Jul 2000 23:19:43 +0100 [thread overview]
Message-ID: <200007282223.XAA13499@hyperion.valhalla.net> (raw)
Well I've applied this across the machines I've got that boot linux (still
haven't commissioned the G4).
Using Ben's 2.2.17pre13ben2. + IRQ_blocking patch + dmasound patch (separate
message)
The good news - is that it's stable & OK on
G3 beige minitower,
G3 Lombard
604e 9600/233
The bad news is that there are high interrupt latencies across the board:
As Ben suggested would be the case, the Lombard is worst (it's the only one
based on ide) but
all three produce >250 us blocks quite easily (ll_rw_blk.c)
and the
9600 (which *was* until two weeks ago my studio machine - quite capable of
recording 12 channels of 44k audio direct to disk under MacOS) produces
400-700 us in scsi without really trying to load it.
Ah well.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-07-28 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200007282223.XAA13499@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--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).