From: Keir Fraser <keir@xen.org>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: Reducing I/O introduced domain scheduling
Date: Tue, 12 Oct 2010 09:47:59 +0100 [thread overview]
Message-ID: <C8D9DF4F.25A79%keir@xen.org> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B22FECF230@shsmsx501.ccr.corp.intel.com>
On 12/10/2010 08:19, "Dong, Eddie" <eddie.dong@intel.com> wrote:
>> First of all have you tested with PV drivers? Performance tests with
>> no PV drivers are not that interesting.
>
> We used PV driver as more as possible, however the C disk in Windows guest
> doesn't support PV yet. (A task in BIOS side or Win HAL side?)
Running the system disk in PV mode certainly works okay with the Citrix PV
drivers. Might this simply be a current limitation of the GPLPV drivers? If
so, I definitely think you are better off putting effort into removing that
limitation, rather than implementing your proposed optimisation. You will
definitely get a bigger perf boost that way, and no suspicious hypervisor
hacks needed.
Cc'ing James Harper, who will best know what the current GPLPV drivers
can/can't do. Also Paul Durrant, who can likely help with advice on how to
PV up the Windows system disk.
-- Keir
next prev parent reply other threads:[~2010-10-12 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 1:12 Reducing I/O introduced domain scheduling Dong, Eddie
2010-10-12 6:38 ` Keir Fraser
2010-10-12 7:19 ` Dong, Eddie
2010-10-12 8:47 ` Keir Fraser [this message]
2010-10-12 8:55 ` James Harper
2010-10-12 9:15 ` Paul Durrant
2010-10-12 9:18 ` Keir Fraser
2010-10-12 9:30 ` Paul Durrant
2010-10-12 9:44 ` Keir Fraser
2010-10-12 9:46 ` Tim Deegan
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=C8D9DF4F.25A79%keir@xen.org \
--to=keir@xen.org \
--cc=Paul.Durrant@citrix.com \
--cc=eddie.dong@intel.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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.