From: Steven Smith <sos22-xen@srcf.ucam.org>
To: Steve Dobbelstein <steved@us.ibm.com>
Cc: xen-devel@lists.xensource.com, sos22@srcf.ucam.org
Subject: Re: Paravirtualised drivers for fully virtualised domains, rev9
Date: Sat, 12 Aug 2006 09:32:23 +0100 [thread overview]
Message-ID: <20060812083223.GA2029@cam.ac.uk> (raw)
In-Reply-To: <OF86C2FBB0.C38A163E-ON052571C7.00550CA7-052571C7.005DC552@us.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2058 bytes --]
> > > Here is what I have found so far in trying to chase down the cause of
> the
> > > slowdown.
> > > The qemu-dm process is running 99.9% of the CPU on dom0.
> > That seems very wrong. When I try this, the device model is almost
> > completely idle. Could you see what strace says, please, or if there
> > are any strange messages in the /var/log/qemu-dm. file?
> Looks like I jumped the gun in relating the 99.9% CPU usage for qemu-dm and
> the network. I start up the HVM domain and without running any tests
> qemu-dm is chewing up 99.9% of the CPU in dom0. So it appears that the
> 100% CPU qemu usage is a problem by itself. Looks like the same problem
> Harry Butterworth is seeing.
qemu-dm misbehaving could certainly lead to the netif going very
slowly.
> > 2) How often is the event channel interrupt firing according to
> > /proc/interrupts? I see about 50k-150k/second.
> I'm seeing ~ 500/s when netpipe-tcp reports decent throughput at smaller
> buffer sizes and then ~50/s when the throughput drops at larger buffer
> sizes.
How large do they have to be to cause problems?
> > The other thing is that these drivers seem to be very sensitive to
> > kernel debugging options in the domU. If you've got anything enabled
> > in the kernel hacking menu it might be worth trying again with that
> > switched off.
> Kernel debugging is on. I also have Oprofile enabled. I'll build a kernel
> without those and see if it helps.
Worth a shot. It shouldn't cause the problems with qemu, though.
> > > It appears there is some interaction between using the xen-vnif
> > > driver and the qemu timer code. I'm still exploring.
> > I'd be happier if I could reproduce this problem here. Are you
> > running SMP? PAE? 64 bit? What kernel are you running in the domU?
> UP kernels in both the domU and dom0 (although the scheduler likes to move
> the 1 vcpu in dom0 around to different physical CPUs). 64-bit kernels on
> both.
I've mostly been testing with 32 bit PAE. I'll have a go with a 64
bit system on Monday.
Thanks,
Steven.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-08-12 8:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 12:51 Paravirtualised drivers for fully virtualised domains Steven Smith
2006-07-18 13:45 ` Ben Thomas
2006-07-18 16:00 ` Steve Ofsthun
2006-07-18 16:23 ` Mark Williamson
2006-07-18 20:34 ` Steven Smith
2006-07-18 23:24 ` Steve Ofsthun
2006-07-19 6:50 ` Gerd Hoffmann
2006-07-26 15:34 ` Steven Smith
2006-08-08 9:42 ` Steven Smith
2006-08-09 18:05 ` Steve Dobbelstein
2006-08-10 11:08 ` Paravirtualised drivers for fully virtualised domains, rev9 Steven Smith
2006-08-10 21:48 ` Steve Dobbelstein
2006-08-11 10:17 ` Steven Smith
2006-08-11 10:31 ` Harry Butterworth
2006-08-14 9:12 ` Steven Smith
2006-08-11 17:04 ` Steve Dobbelstein
2006-08-12 8:32 ` Steven Smith [this message]
2006-08-14 21:22 ` Steve Dobbelstein
2006-08-15 7:27 ` Steven Smith
2006-08-15 22:05 ` Steve Dobbelstein
2006-08-16 13:36 ` Steven Smith
2006-08-16 13:33 ` Paravirtualised drivers for fully virtualised domains, rev11 sos22-xen
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=20060812083223.GA2029@cam.ac.uk \
--to=sos22-xen@srcf.ucam.org \
--cc=sos22@srcf.ucam.org \
--cc=steved@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.