public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andrew Theurer <habanero@linux.vnet.ibm.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] don't call adjust_vmx_controls() second time
Date: Mon, 31 Aug 2009 16:52:14 +0300	[thread overview]
Message-ID: <4A9BD58E.3050302@redhat.com> (raw)
In-Reply-To: <4A9BCA96.8060505@linux.vnet.ibm.com>

On 08/31/2009 04:05 PM, Andrew Theurer wrote:
>> How does it compare to the other hypervisor now?
>
>
> My original results for other hypervisor were a little inaccurate.  
> They mistakenly used 2 vcpu guests. New runs with 1 vcpu guests (as 
> used in kvm) have slightly lower CPU utilization.  Anyway, here's the 
> breakdown:
>
>                                CPU       percent more CPU
> kvm-master/qemu-kvm-87:        50.15     78%
> kvm-next/qemu-kvm-87:          37.73     34%
>

Much better, though still a lot of work to do.

>>>> 25278     1.5214  vmlinux-2.6.31-rc5-autokern1 native_write_msr_safe
>>>> 12278     0.7390  vmlinux-2.6.31-rc5-autokern1 native_read_msr_safe
>>
>> This will be reduced to if we move virtio to kernel context.
>
> Are there plans to move that to kernel for disk, too?

We don't know if disk or net contributed to this.  If it turns out that 
vhost-blk makes sense, we'll do it.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-08-31 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 15:41 [PATCH] don't call adjust_vmx_controls() second time Gleb Natapov
2009-08-27 16:21 ` Avi Kivity
2009-08-27 20:42   ` Andrew Theurer
2009-08-30  8:59     ` Avi Kivity
2009-08-31 13:05       ` Andrew Theurer
2009-08-31 13:52         ` 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=4A9BD58E.3050302@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    /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