All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommi Virtanen <tv@tv.debian.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: Serious performance issues
Date: Mon, 07 Mar 2005 08:51:21 +0200	[thread overview]
Message-ID: <422BF9E9.8000501@tv.debian.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3456@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
> Have you got some interrupt line going crazy?

That seems to be the problem.

In native linux, I see:

0	timer	1000/s
LOC		1000/s

and in xen dom0 I see:

21	uhci_hcd	35000/s
130	timer		45000/s

rmmodding uhci_hcd removes irq 21, but makes the timer
speed up to 115000/s.

rmmod ohci13943, rmmod ehci_hcd makes the timer go
800000/s.

rmmoding even more drivers puts the peak at 1100000/s,
until it suddenly drops to 30/s. Didn't check between each
rmmod, so I don't know which exact one caused it.

Unplugging my USB trackball and modprobing _all_ of the drivers above
causes timer to tick at 60/s. Plugging in my USB trackball makes it
33000/s. Unplugging has no effect.

Booting up with trackball unconnected gives about 30000/s, too, so
it's not just the USB mouse driver. It seems there is a problem with
USB.

But that doesn't explain everything. It seems the bridge module has
trouble, too. rmmod bridge, or just ip li set dev br0 down makes timer
go from crazy to normal, too.

Thanks for the hint, I think I can manage to find a working
configuration based on this. Of course, having no such problems in the
first place would be even better.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-07  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 17:44 Serious performance issues Ian Pratt
2005-03-07  6:51 ` Tommi Virtanen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07  9:47 Ian Pratt
2005-03-07 15:11 ` Nuutti Kotivuori
2005-03-07  8:19 Ian Pratt
2005-03-07  9:23 ` Tommi Virtanen
2005-03-07 19:19   ` Nuutti Kotivuori
2005-03-07  8:04 Ian Pratt
2005-03-07  7:11 ` Tommi Virtanen
2005-03-04 17:48 Ian Pratt
2005-03-04 18:57 ` Tommi Virtanen
2005-03-03 21:57 Tommi Virtanen
2005-03-04 15:52 ` Anthony Liguori
2005-03-04 18:55   ` Tommi Virtanen

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=422BF9E9.8000501@tv.debian.net \
    --to=tv@tv.debian.net \
    --cc=ian.pratt@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.