From: Marcus Granado <marcus.granado@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Matthew Portas <matthew.portas@citrix.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Performance of Xen VCPU Scheduling
Date: Wed, 10 Jul 2013 15:46:01 +0100 [thread overview]
Message-ID: <51DD73A9.5070408@citrix.com> (raw)
In-Reply-To: <1373462584.3051.83.camel@Solace>
On 10/07/13 14:23, Dario Faggioli wrote:
> On mer, 2013-07-10 at 14:00 +0100, Marcus Granado wrote:
>>
>> While trying to understand why this increased performance is not present
>> in the default non-pinned state and if it would be possible to obtain
>> this extra performance in the default non-pinned dom0 configuration,
>> Matthew Portas and I evaluated lots of Xen 4.2 parameters and patches:
>>
>
> Just one point. This by any means make all this study/effort less
> valuable (quite the contrary, actually), but, with George, we started to
> discuss about bringing credit2 into a better shape and, at some point,
> switch to it by default. It's unclear whether this could be done for
> 4.4, but still... So, do you have any numbers about it already?
Yes, I believe we have a couple of results for credit2, I'll put them on
the page.
> How hard
> will it be to, at some point, perform the same measurements and analysis
> with it?
>
Easy enough, all the measurements used automated tests to improve
reproducibility. We would need a url with binaries or rpms as input, and
the output is a set of graphs for analysis.
cheers,
Marcus
next prev parent reply other threads:[~2013-07-10 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 13:00 Performance of Xen VCPU Scheduling Marcus Granado
2013-07-10 13:23 ` Dario Faggioli
2013-07-10 14:46 ` Marcus Granado [this message]
2013-07-10 14:55 ` Dario Faggioli
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=51DD73A9.5070408@citrix.com \
--to=marcus.granado@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=matthew.portas@citrix.com \
--cc=xen-devel@lists.xensource.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.