From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@hamnavoe.com, 9fans@9fans.net
Subject: Re: [9fans] usb slowness
Date: Mon, 5 Mar 2012 11:14:05 -0500 [thread overview]
Message-ID: <fe8ef0a75d1607cc6a5dec35fefe67db@chula.quanstro.net> (raw)
In-Reply-To: <a6215b50dd4c0d5807e9bf72b06d411d@hamnavoe.com>
On Mon Mar 5 11:06:43 EST 2012, 9fans@hamnavoe.com wrote:
> > if you could temporarly run a 9atom kernel,
>
> With the normal kernel, you can use acid or db to look at the intrtimes
> array to see the spread of cpu times used in each interrupt vector entry.
>
> See http://9fans.net/archive/2003/11/520
i didn't find the original histogram very useful. it is not scaled
by the speed of the processor nor type of interrupt. the slots
in the histogram are appropriate for 8259 interrupts on a 2000-era
processor (100µs increments). almost all the interrupts i see are
< 20µs. the 82598 on my relativly slow cpu server averages 2.5µs
per interrupt.
it's also a pain to print out without a file in addition to /dev/irqalloc.
i found the absolute count and absolute # of cpu cycles (to avoid
predivision sloppiness) to be a lot more useful for the general case.
a hisogram sure could be useful, but i think i'd want to taylor it to
a specific problem. and i haven't had one yet.
- erik
next prev parent reply other threads:[~2012-03-05 16:14 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 [this message]
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
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=fe8ef0a75d1607cc6a5dec35fefe67db@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=9fans@hamnavoe.com \
/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).