From: erik quanstrom <quanstro@quanstro.net>
To: 9p-st@imu.li, 9fans@9fans.net
Subject: Re: [9fans] usb slowness
Date: Tue, 6 Mar 2012 13:55:49 -0500 [thread overview]
Message-ID: <48dfd79dc45c0d5e9d88c6a79de7202e@brasstown.quanstro.net> (raw)
In-Reply-To: <2579b9.228186c7.D0Vx.mx@tumtum.plumbweb.net>
On Tue Mar 6 10:37:06 EST 2012, 9p-st@imu.li wrote:
> > my working theory is that i'm getting all the interrupts, but not soon
> > enough... the fascinating piece is that the olpc and the pc with intel
> > ehc take just about the same amount of time.
>
> indeed, if i set the interrupt threshold control to 1 micro-frame (they
> default to 8), i get 10-11 sec dd, say, half as slow. and ping time to my
> switch is half. and i can get about twice the throughput from the file
> server, which is still kinda slow.
>
> (hget yields about 6Mbit over a 100Mbit link)
it sounds like you have it all figured out. but just in case there is a spurious
interrupt causing trouble, you can check with this rather embarassing acid
script. sorry, i can't get acid to recoginze intrcountx as a vlong.
acid -l acid -k 1 /386/9pccpu
acid: i=0; while i<256*2 do {if(intrcountx[i]>0) then {print(i/2\D, "\t", intrcountx[i]);} i=i+2;}
7 143
14 44355
50 99090099
65 19938
73 37571
145 9814
153 1
161 42
169 7
- erik
next prev parent reply other threads:[~2012-03-06 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 1:56 Tristan
2012-03-05 15:46 ` erik quanstrom
2012-03-05 16:05 ` Richard Miller
2012-03-05 16:14 ` erik quanstrom
2012-03-05 16:20 ` Richard Miller
2012-03-06 13:19 ` Tristan
2012-03-06 15:36 ` Tristan
2012-03-06 16:10 ` Richard Miller
2012-03-06 18:55 ` erik quanstrom [this message]
2012-03-06 22:22 ` Tristan
2012-03-07 5:50 ` Tristan
2012-03-07 5:53 ` Tristan
2012-03-07 9:31 ` Charles Forsyth
2012-03-10 3:13 ` [9fans] donehead changed before ack Tristan
2012-03-10 12:33 ` erik quanstrom
2012-03-10 15:14 ` Tristan
2012-03-07 15:27 ` [9fans] usb slowness Richard Miller
2012-03-05 15:56 ` Richard Miller
2012-03-06 0:01 ` Tristan
2012-03-06 10:39 ` Richard Miller
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=48dfd79dc45c0d5e9d88c6a79de7202e@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=9p-st@imu.li \
/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).