From: Chris Van Horne <cvanhorne@cox.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slow throughput on wavelan/epro100
Date: Sun, 8 Feb 2004 21:57:41 -0700 [thread overview]
Message-ID: <40271345.8040705@cox.net> (raw)
In-Reply-To: <2935bcc643e24c92afff05f2224b1cd8@plan9.bell-labs.com>
Yep, ether{0,1} are both on IRQ 11.
David Presotto wrote:
>Check to see where plan9 decided to assign its interrupts (cat '#P'/irqalloc).
>Then check to see what they are on whatever OS you were running.
>
>
> ------------------------------------------------------------------------
>
> Subject:
> [9fans] slow throughput on wavelan/epro100
> From:
> Chris Van Horne <cvanhorne@cox.net>
> Date:
> Sun, 08 Feb 2004 20:18:32 -0700
> To:
> 9fans@cse.psu.edu
>
> To:
> 9fans@cse.psu.edu
>
>
> I noticed yesterday after throwing p9 on a toshiba satellite 2805-S301
> under a Linksys WPC11 that the network throughput was a horrid 26
> kB/sec. The onboard Intel epro100 gave only 640 kB/sec. Anyone have
> some ideas that could lead to this or something I could try?
>
> Not sure what other information is needed, but:
> 128MB RAM, using fossil, disk doesn't feel sluggish.
next prev parent reply other threads:[~2004-02-09 4:57 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 [this message]
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
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=40271345.8040705@cox.net \
--to=cvanhorne@cox.net \
--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).