From: Avi Kivity <avi@redhat.com>
To: akataria@vmware.com
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org
Subject: Re: Paravirtualization on VMware's Platform [VMI].
Date: Sat, 19 Sep 2009 10:43:40 +0300 [thread overview]
Message-ID: <4AB48BAC.1000409@redhat.com> (raw)
In-Reply-To: <1253233028.19731.63.camel@ank32.eng.vmware.com>
On 09/18/2009 03:17 AM, Alok Kataria wrote:
> Hi,
>
> We ran a few experiments to compare performance of VMware's
> paravirtualization technique (VMI) and hardware MMU technologies (HWMMU)
> on VMware's hypervisor.
>
> To give some background, VMI is VMware's paravirtualization
> specification which tries to optimize CPU and MMU operations of the
> guest operating system. For more information take a look at this
> http://www.vmware.com/interfaces/paravirtualization.html
>
> In most of the benchmarks, EPT/NPT (hwmmu) technologies are at par or
> provide better performance compared to VMI.
> The experiments included comparing performance across various micro and
> real world like benchmarks.
>
We've reached a similar conclusion for kvm pvmmu vs ept/npt.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-09-19 7:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 0:17 Paravirtualization on VMware's Platform [VMI] Alok Kataria
2009-09-18 0:34 ` Chris Wright
2009-09-18 0:53 ` Jeremy Fitzhardinge
2009-09-18 0:58 ` Chris Wright
2009-09-18 1:43 ` Alok Kataria
2009-09-19 7:43 ` Avi Kivity [this message]
2009-09-19 22:44 ` Greg KH
2009-09-20 1:04 ` Jeremy Fitzhardinge
2009-09-20 3:56 ` Alok Kataria
2009-09-20 3:59 ` Alok Kataria
2009-09-20 7:42 ` Ingo Molnar
2009-09-20 7:52 ` Arjan van de Ven
2009-09-20 9:00 ` Avi Kivity
2009-09-20 15:49 ` Jeremy Fitzhardinge
2009-09-20 19:00 ` Avi Kivity
2009-09-22 8:09 ` Ingo Molnar
2009-09-22 16:52 ` Jeremy Fitzhardinge
2009-09-22 18:02 ` Ingo Molnar
2009-09-22 18:16 ` Jeremy Fitzhardinge
2009-09-22 19:04 ` Ingo Molnar
2009-09-22 19:30 ` Jeremy Fitzhardinge
2009-09-22 7:22 ` Rusty Russell
2009-09-22 16:53 ` Jeremy Fitzhardinge
2009-09-22 19:30 ` Alok Kataria
2009-09-22 19:47 ` Jeremy Fitzhardinge
2009-09-22 21:27 ` H. Peter Anvin
2009-09-22 21:54 ` Alok Kataria
2009-09-22 22:58 ` H. Peter Anvin
2009-09-23 7:29 ` Gerd Hoffmann
2009-09-29 0:45 ` Alok Kataria
2009-09-29 2:25 ` H. Peter Anvin
2009-09-29 3:00 ` Alok Kataria
2009-09-29 9:01 ` Chris Wright
2009-09-29 17:25 ` Alok Kataria
2009-09-29 17:27 ` H. Peter Anvin
2009-09-29 17:36 ` Alok Kataria
2009-09-29 18:21 ` Chris Wright
2009-09-29 8:08 ` Arjan van de Ven
2009-09-29 16:49 ` Alok Kataria
2009-09-29 16:51 ` H. Peter Anvin
2009-09-29 17:55 ` Learning question regarding virtio and partvirt_ops Hank Janssen
2009-09-29 19:02 ` Brian Jackson
2009-10-02 3:00 ` Paravirtualization on VMware's Platform [VMI] Eric W. Biederman
2009-10-02 4:45 ` Alok Kataria
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=4AB48BAC.1000409@redhat.com \
--to=avi@redhat.com \
--cc=akataria@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.osdl.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).