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: Tue, 15 Aug 2006 08:27:50 +0100 [thread overview]
Message-ID: <20060815072750.GA2610@cam.ac.uk> (raw)
In-Reply-To: <OF2D476D08.8323F190-ON052571CA.00703F37-052571CA.00756F81@us.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]
> > > 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.
> Agreed. I applied the patch to sent to Harry. I appears to fix the 99.9%
> CPU usage problem.
Great, thanks.
> > > > 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?
> I'm noticing a drop off in throughput at a buffer size of 3069. Here is a
> snip from the output from netpipe-tcp.
What are the MTUs on the interfaces, according to ifconfig, in dom0
and domU?
> I don't know offhand why the throughput drops off. I'll look into it. Any
> tips would be helpful.
tcpdump in the domU and dom0 might be enlightening, just to see if any
packets are getting dropped or truncated. The connections probably
slow enough when it's misbehaving for it to keep up.
Are you running through the bridge? It's unlikely to be that, but it
would be good to eliminate it as a variable by doing some domU<->dom0
tests without it involved.
What version of Linux are you running in the domU? Does it have any
patches applied?
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-15 7:27 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
2006-08-14 21:22 ` Steve Dobbelstein
2006-08-15 7:27 ` Steven Smith [this message]
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=20060815072750.GA2610@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.