public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: lidong chen <chen.lidong.kernel@gmail.com>,
	mst@redhat.com, aliguori@us.ibm.com, rusty@rustcorp.com.au,
	kvm@vger.kernel.org
Subject: Re: Performance test result between virtio_pci MSI-X disable and enable
Date: Tue, 23 Nov 2010 08:42:14 +0200	[thread overview]
Message-ID: <20101123064213.GO7948@redhat.com> (raw)
In-Reply-To: <4CEB5D23.6040809@redhat.com>

On Tue, Nov 23, 2010 at 08:20:19AM +0200, Avi Kivity wrote:
> On 11/23/2010 04:53 AM, lidong chen wrote:
> >Test method:
> >Send the same traffic load between virtio_pci MSI-X disable and
> >enable,and compare the cpu rate of host os.
> >I used the same version of virtio driver, only modify the msi-x option.
> >the host os version is 2.6.32.
> >the virtio dirver is from rhel6.
> >the guest version  os is 2.6.16.
> >
> >Test result:
> >with msi-x disable, the cpu rate of host os is 110%.
> >with msi-x enable, the cpu rate of host os is 140%.
> >
> ...
> 
> >Conclusion:
> >msi-x enable waste more cpu resource is caused by MSIX mask bit. In
> >older kernels program this bit twice
> >on every interrupt. and caused ept violation.
> >
> >So I think we should add a param to control this.with older kernels,
> >we should disable MSIX.
> >And I think this should deal by qemu.
> 
> There is now work in progress (by Sheng Yang) to speed up mask bit
> emulation, which should improve things.  Also, newer kernels don't
> hit the mask bit so hard.  You might try to backport the mask bit
> patches to your 2.6.16 guest.
> 
And IIRC we do have option to disable MSIX in qemu. I just don't
remember how it looks. Michael?

--
			Gleb.

  reply	other threads:[~2010-11-23  6:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  2:53 Performance test result between virtio_pci MSI-X disable and enable lidong chen
2010-11-23  6:20 ` Avi Kivity
2010-11-23  6:42   ` Gleb Natapov [this message]
2010-11-23  7:27   ` lidong chen
2010-11-23  7:39     ` Avi Kivity
2010-11-30  9:10       ` lidong chen
2010-11-30  9:24         ` Yang, Sheng
2010-12-01  8:41           ` lidong chen
2010-12-01  8:49             ` Yang, Sheng
2010-12-01  8:54               ` lidong chen
2010-12-01  9:02                 ` Yang, Sheng
2010-12-01  9:29                   ` lidong chen
2010-12-01  9:37                     ` Yang, Sheng
2010-12-01  9:34                   ` Yang, Sheng
2010-12-01  8:56             ` Yang, Sheng
2010-12-01 14:03             ` Michael S. Tsirkin
2010-12-02  1:13               ` Yang, Sheng
2010-12-02  9:49                 ` Michael S. Tsirkin
2010-12-02 11:52                   ` Sheng Yang
2010-12-02 12:23                     ` Michael S. Tsirkin
2010-12-02 14:01                       ` lidong chen
2010-12-22 13:52 ` Michael S. Tsirkin

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=20101123064213.GO7948@redhat.com \
    --to=gleb@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=chen.lidong.kernel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    /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