From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <40271345.8040705@cox.net> From: Chris Van Horne User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031221 Thunderbird/0.4 MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] slow throughput on wavelan/epro100 References: <2935bcc643e24c92afff05f2224b1cd8@plan9.bell-labs.com> In-Reply-To: <2935bcc643e24c92afff05f2224b1cd8@plan9.bell-labs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 8 Feb 2004 21:57:41 -0700 Topicbox-Message-UUID: d39d738c-eacc-11e9-9e20-41e7f4b1d025 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 > 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.