9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tristan <9p-st@imu.li>
To: 9fans@9fans.net
Subject: Re: [9fans] usb slowness
Date: Tue,  6 Mar 2012 08:19:22 -0500	[thread overview]
Message-ID: <2579b9.032a3487.pkFh.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <a8a4d75adaf927ca6d650b46859510c5@hamnavoe.com> <504d1e9e6a08271d15827ea4c00507ff@chula.quanstro.net>

> if you could temporarly run a 9atom kernel,

cpu% dd -if /dev/sdU0.0/data -of /dev/null -count 1024 -bs 65536

/dev/irqalloc yields
trap	irq	delta count	delta cycles	type	name
35	3	27648           510854000	i8259	usbehci

which doesn't seem extraordinary. and nothing else is huge either.

mpirq doesn't appear to exist in #P

the whole transfer takes about 8% longer on 9atom.

> > if i force polling, it's a little faster: 0.01u 0.45s 17.70r
> That's interesting - it shouldn't make a difference unless there's
> something wrong with the controller or the driver.  What did you do to
> force polling?

added 'ctrl->poll.must = 1' to init in usbehci.c

> Yes, I think you're right - system cputime will only be incremented for
> a running process.  But you can watch the last column of /dev/sysstat
> (or use 'stats -I') to see the percentage of time spent in interrupt
> handlers.

interrupt time is quite low/very low... (olpc / intel)

> How about number of interrupts?  Erik's theory was that you were
> getting too many of these.

interrupt count is very low/moderate... (olpc / intel)

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.

and a different usb flash device doesn't change it (which was expected as
usb/ether seems to suffer also).

enjoy,
tristan

-- 
All original matter is hereby placed immediately under the public domain.



  parent reply	other threads:[~2012-03-06 13:19 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 [this message]
2012-03-06 15:36     ` Tristan
2012-03-06 16:10       ` Richard Miller
2012-03-06 18:55       ` erik quanstrom
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=2579b9.032a3487.pkFh.mx@tumtum.plumbweb.net \
    --to=9p-st@imu.li \
    --cc=9fans@9fans.net \
    /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).