From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
linux-perf-users@vger.kernel.org
Subject: Re: high load with usb device
Date: Tue, 14 Sep 2010 12:07:56 +0200 [thread overview]
Message-ID: <4C8F497C.7000904@redhat.com> (raw)
In-Reply-To: <4C8F47A1.4030600@msgid.tls.msk.ru>
On 09/14/2010 12:00 PM, Michael Tokarev wrote:
> # strace -p 23020 -p 23023 -c
> Process 23020 attached - interrupt to quit
> Process 23023 attached - interrupt to quit
> ^CProcess 23020 detached
> Process 23023 detached
> % time seconds usecs/call calls errors syscall
> ------ ----------- ----------- --------- --------- ----------------
> 98.98 23.462158 15569 1507 ioctl
> 0.64 0.151725 37 4063 5 futex
> 0.11 0.025051 0 86932 select
> 0.09 0.021188 0 408836 clock_gettime
> 0.07 0.016543 0 271933 136484 read
> 0.04 0.008958 0 181118 gettimeofday
> 0.02 0.005756 0 101190 write
> 0.02 0.005506 0 89180 timer_settime
> 0.02 0.004754 0 96271 timer_gettime
> 0.01 0.002682 0 50595 rt_sigaction
> 0.00 0.000000 0 1 rt_sigpending
> 0.00 0.000000 0 1 1 rt_sigtimedwait
> ------ ----------- ----------- --------- --------- ----------------
> 100.00 23.704321 1291627 136490 total
>
>
Well, well. Translating to rates, we have 63.6 ioctls/sec but 17k
clock_gettime, 11k read() and 4k writes per second. The device model
has gone haywire, somehow without any trace in perf top.
Let's see what those reads and writes are about. Please strace a short
segment again, without -c, and use lsof to see which fds are referenced
in the read and write calls.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-14 10:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 12:21 high load with win7 & usb tablet Michael Tokarev
2010-09-10 11:47 ` Jes Sorensen
2010-09-10 12:16 ` Michael Tokarev
2010-09-10 16:17 ` high load with usb device Michael Tokarev
2010-09-12 9:26 ` Avi Kivity
2010-09-14 6:51 ` Michael Tokarev
2010-09-14 9:06 ` Avi Kivity
2010-09-14 9:08 ` Avi Kivity
2010-09-14 10:00 ` Michael Tokarev
2010-09-14 10:07 ` Avi Kivity [this message]
2010-09-14 10:25 ` Michael Tokarev
2010-09-14 10:39 ` Avi Kivity
2010-09-14 11:02 ` Michael Tokarev
2010-09-14 13:15 ` Michael Tokarev
2010-09-14 13:25 ` Avi Kivity
2010-09-14 13:29 ` Michael Tokarev
2010-09-14 13:38 ` Michael Tokarev
2010-09-14 14:45 ` Avi Kivity
2010-09-14 14:53 ` Michael Tokarev
2010-09-14 16:00 ` Avi Kivity
2010-09-14 16:29 ` Michael Tokarev
2010-09-14 16:37 ` Avi Kivity
2010-09-14 16:50 ` Michael Tokarev
2010-09-14 16:45 ` David S. Ahern
2010-09-14 15:51 ` David S. Ahern
2010-09-14 16:00 ` Michael Tokarev
2010-09-14 16:09 ` David S. Ahern
2010-09-10 12:19 ` high load with win7 & usb tablet Avi Kivity
2010-09-10 12:44 ` Michael Tokarev
2010-09-10 12:50 ` Avi Kivity
[not found] ` <4C8A44E6.2060008@msgid.tls.msk.ru>
2010-09-10 14:56 ` Avi Kivity
2010-09-10 15:03 ` Michael Tokarev
2010-09-10 16:03 ` Avi Kivity
2010-09-14 8:26 ` Brad Campbell
2010-09-14 8:33 ` Michael Tokarev
2010-09-14 8:46 ` Brad Campbell
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=4C8F497C.7000904@redhat.com \
--to=avi@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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