From: Avi Kivity <avi@redhat.com>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Mark McLoughlin <markmc@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Network throughput limits for local VM <-> VM communication
Date: Thu, 18 Jun 2009 11:37:38 +0300 [thread overview]
Message-ID: <4A39FCD2.6080507@redhat.com> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E67D301B624@GVW1118EXC.americas.hpqcorp.net>
On 06/17/2009 06:41 PM, Fischer, Anna wrote:
> It still does not answer my question on why I only see low CPU utilization numbers with the e1000 virtual device model. There is no network stalling or packet drops or any other obvious issues when running with that model, but I am still seeing low CPU utilization numbers. What is preventing KVM here to use more of the host CPU capacity when the host is not doing anything else but run virtual machines? Is there any way that I can get higher CPU utilization out of KVM?
>
A missing wakeup might cause this, but I really have no idea how we can
trace the cause.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-18 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 11:06 Network throughput limits for local VM <-> VM communication Fischer, Anna
2009-06-09 13:39 ` Mark McLoughlin
2009-06-09 13:55 ` Fischer, Anna
2009-06-10 13:29 ` Arnd Bergmann
2009-06-10 13:57 ` Fischer, Anna
2009-06-11 7:49 ` Arnd Bergmann
2009-06-11 8:01 ` Fischer, Anna
2009-06-11 8:17 ` Avi Kivity
2009-06-11 8:46 ` Fischer, Anna
2009-06-11 8:50 ` Avi Kivity
2009-06-17 7:36 ` Fischer, Anna
2009-06-17 7:50 ` Avi Kivity
2009-06-17 8:12 ` Fischer, Anna
2009-06-17 12:22 ` Avi Kivity
2009-06-17 15:41 ` Fischer, Anna
2009-06-18 8:37 ` Avi Kivity [this message]
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=4A39FCD2.6080507@redhat.com \
--to=avi@redhat.com \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.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.