From: Dario Faggioli <dario.faggioli@citrix.com>
To: Massimo Canonico <mex@di.unipmn.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: CAP and performance problem
Date: Thu, 6 Jun 2013 11:52:58 +0200 [thread overview]
Message-ID: <1370512378.18519.244.camel@Solace> (raw)
In-Reply-To: <51B04F0E.5040506@di.unipmn.it>
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
On gio, 2013-06-06 at 10:57 +0200, Massimo Canonico wrote:
> On 06/06/2013 10:37 AM, Dario Faggioli wrote:
> > On mer, 2013-06-05 at 19:05 +0200, Massimo Canonico wrote:
> >> Hi Dario,
> >> and thanks for these test.
> >>
> >> I forgot to ask you which xen version has beed used for your experiments.
> >>
> > Yeah, me too! :-)
> >
> > I'm using xen-unstable, pulled yesterday (commit id
> > e430510e5cbbfcdc1077739292def633e70fedea), compiled and installed on a
> > Debian unstable system. Dom0 kernel is a bit old, as it's a 3.6.
> >
> > What about you?
> xen 4.2.2
> kernel dom0: 3.8.11-200.fc18.x86_64
>
I see. There shouldn't be much differences, from a credit scheduler
point of view (and even more so wrt the caps) between 4.2 and unstable.
Anyway, just to rule out all the possible doubts, can you build and
install unstable on your box?
What about the guest? PV or HVM? What's running in there? In my case it
was a PV guest, also running a Debian unstable, and using the same
kernel dom0 does.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-06 9:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:02 CAP and performance problem Massimo Canonico
2013-05-21 10:41 ` George Dunlap
2013-05-21 10:48 ` George Dunlap
2013-05-21 11:54 ` Massimo Canonico
2013-05-21 13:06 ` Dario Faggioli
2013-05-21 14:28 ` Massimo Canonico
2013-05-21 14:47 ` Dario Faggioli
2013-05-21 15:26 ` Massimo Canonico
2013-05-22 14:42 ` Massimo Canonico
2013-05-22 15:39 ` Dario Faggioli
2013-05-24 7:48 ` Massimo Canonico
2013-06-04 14:03 ` Massimo Canonico
2013-06-04 14:25 ` Dario Faggioli
2013-06-05 16:50 ` Dario Faggioli
2013-06-05 17:11 ` Dario Faggioli
2013-06-05 17:05 ` Massimo Canonico
2013-06-06 8:37 ` Dario Faggioli
2013-06-06 8:57 ` Massimo Canonico
2013-06-06 9:52 ` Dario Faggioli [this message]
2013-06-06 10:39 ` Juergen Gross
2013-06-06 10:44 ` George Dunlap
2013-06-06 12:52 ` Massimo Canonico
2013-06-06 12:58 ` George Dunlap
2013-06-06 13:02 ` Juergen Gross
2013-06-06 13:55 ` Massimo Canonico
2013-06-06 14:12 ` George Dunlap
2013-06-06 14:12 ` Dario Faggioli
2013-06-06 15:27 ` Massimo Canonico
2013-06-06 15:42 ` Dario Faggioli
2013-06-06 15:54 ` Dario Faggioli
2013-06-06 16:27 ` George Dunlap
2013-06-07 7:40 ` Massimo Canonico
2013-06-07 4:45 ` Juergen Gross
2013-06-06 13:03 ` Dario Faggioli
2013-06-06 13:09 ` Massimo Canonico
2013-06-06 9:02 ` George Dunlap
2013-06-06 9:48 ` 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=1370512378.18519.244.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=mex@di.unipmn.it \
--cc=xen-devel@lists.xen.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).