From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Keir@acsinet13.oracle.com, Fraser <keir.xen@gmail.com>
Subject: Re: HYBRID: PV in HVM container
Date: Fri, 29 Jul 2011 11:48:52 -0400 [thread overview]
Message-ID: <20110729154852.GI5458@dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107281229260.12963@kaball-desktop>
On Thu, Jul 28, 2011 at 12:34:42PM +0100, Stefano Stabellini wrote:
> On Thu, 28 Jul 2011, Mukesh Rathor wrote:
> > Hi folks,
> >
> > Well, I did some benchmarking and found interesting results. Following
> > runs are on a westmere with 2 sockets and 10GB RAM. Xen was booted
> > with maxcpus=2 and entire RAM. All guests were started with 1vcpu and 2GB
> > RAM. dom0 started with 1 vcpu and 704MB. Baremetal was booted with 2GB
> > and 1 cpu. HVM guest has EPT enabled. HT is on.
> >
> > So, unless the NUMA'ness interfered with results (using some memory on
> > remote socket), it appears HVM does very well. To the point that it
> > seems a hybrid is not going to be worth it. I am currently running
> > tests on a single socket system just to be sure.
> >
>
> The high level benchmarks I run to compare PV and PV on HVM guests show
> a very similar scenario.
>
> It is still worth having HYBRID guests (running with EPT?) in order to
> support dom0 in an HVM container one day not too far from now.
I am just wondering how much dom0 cares about this? I mean if you use
blkback, netback - etc - they are all in the kernel. The device drivers
are also in the kernel.
Based on Mukeshs's results the PVonHVM work you did really paid
itself off for guests. The numbers are even better than baremetal .. which
I am bit surprised - maybe the collecting of the data (gettimeofday) is
not the best?
next prev parent reply other threads:[~2011-07-29 15:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 19:24 HYBRID: PV in HVM container Mukesh Rathor
2011-06-27 19:36 ` Keir Fraser
2011-06-28 1:51 ` Mukesh Rathor
2011-06-28 7:46 ` Keir Fraser
2011-06-28 8:30 ` Ian Campbell
2011-06-28 8:35 ` Keir Fraser
2011-06-28 8:49 ` Ian Campbell
2011-06-28 10:46 ` Stefano Stabellini
2011-06-28 10:50 ` Ian Campbell
2011-06-28 18:32 ` Mukesh Rathor
2011-06-28 18:39 ` Keir Fraser
2011-06-28 8:31 ` Ian Campbell
2011-06-28 17:56 ` Mukesh Rathor
2011-07-01 1:54 ` Mukesh Rathor
2011-07-09 1:53 ` Mukesh Rathor
2011-07-09 7:35 ` Keir Fraser
2011-07-28 1:58 ` Mukesh Rathor
2011-07-28 11:34 ` Stefano Stabellini
2011-07-29 15:48 ` Konrad Rzeszutek Wilk [this message]
2011-07-29 16:41 ` Stefano Stabellini
2011-07-29 17:28 ` Konrad Rzeszutek Wilk
2011-07-29 18:00 ` Stefano Stabellini
2011-07-29 18:00 ` Konrad Rzeszutek Wilk
2011-07-29 18:16 ` Stefano Stabellini
2011-08-09 8:54 ` Ian Campbell
2011-08-17 19:27 ` Jeremy Fitzhardinge
2011-07-29 15:43 ` Konrad Rzeszutek Wilk
2011-11-17 23:38 ` Mukesh Rathor
2011-11-18 12:21 ` Stefano Stabellini
2011-11-19 0:17 ` Mukesh Rathor
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=20110729154852.GI5458@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Keir@acsinet13.oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=stefano.stabellini@eu.citrix.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 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).