From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: jsun@mvista.com
Subject: update: ppc IRQ blocking.
Date: Sun, 16 Jul 2000 12:55:57 +0100 [thread overview]
Message-ID: <200007161155.MAA19420@hyperion.valhalla.net> (raw)
Hi,
Well, much of the info presented in my message yesterday was bogus...
The instrumentation needs improvement... it's missing too many cases where
IRQs are switched on/off behind the back of the measurement (which is making
it very difficult to narrow down the rogue...)
I'm working on it.
The latency measurements *do* indicate a problem... I don't think that is
bogus.. but...
So unless:
(a) you have an idea where there might be a 8 to 10ms hold off in IRQ or
(b) you already have an IRQ blocking measurement set that includes all the
cases (in which case I'd love a copy ;-)
Ignore the post of yesterday...
Iain.
P.S. Jun - do you want a copy of what I've got so far? or wait 'till it's
done... I covered a lot more cases but still need to deal with all the stuff
going on in head.S :-(
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-16 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-16 11:55 Iain Sandoe [this message]
2000-07-17 20:05 ` update: ppc IRQ blocking Jun Sun
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=200007161155.MAA19420@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).