From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slow throughput on wavelan/epro100
Date: Mon, 9 Feb 2004 09:56:29 -0500 [thread overview]
Message-ID: <fc663c189b2ce5cb37b2c77f71c3ca69@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402082232100.18308-100000@maxroach.lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 187 bytes --]
You can see interrupts in general (/dev/sysstat or the stats program). However
they don't get broken out by device or interrupt level. Easy enough to do for
irq. I'll add it to '#P'.
[-- Attachment #2: Type: message/rfc822, Size: 2862 bytes --]
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slow throughput on wavelan/epro100
Date: Sun, 8 Feb 2004 22:33:49 -0700 (MST)
Message-ID: <Pine.LNX.4.44.0402082232100.18308-100000@maxroach.lanl.gov>
On Sun, 8 Feb 2004, Chris Van Horne wrote:
> chipset: Intel 82371AB PIIX4
>
> The PCMCIA yenta is showing on IRQ 11, as is the e100, while the wavelan
> (WPC11 v3) is on IRQ 3.
somebody remind me. How do we see whether plan9 is taking interrupts from
those devices? Sorry, I know the simple command on linux but forget it on
Plan 9. You can do some pings via the wavelan and see if you are getting
tx ints or not, and if not, that's a place to start looking (you've
probably done this).
ron
next prev parent reply other threads:[~2004-02-09 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 3:43 David Presotto
2004-02-09 4:57 ` Chris Van Horne
2004-02-09 5:04 ` ron minnich
2004-02-09 5:19 ` Chris Van Horne
2004-02-09 5:33 ` ron minnich
2004-02-09 5:41 ` jmk
2004-02-09 6:00 ` ron minnich
2004-02-09 14:56 ` David Presotto [this message]
2004-02-09 15:03 ` Charles Forsyth
2004-02-09 5:34 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 3:18 Chris Van Horne
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=fc663c189b2ce5cb37b2c77f71c3ca69@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).