All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "george.dunlap@eu.citrix.com" <george.dunlap@eu.citrix.com>,
	xen-devel@lists.xenproject.org, jtweaver@hawaii.edu
Subject: Re: Status of Credit2 and Credit1 [was: Re: Xen 4.6 Development Update (four months reminder)]
Date: Wed, 20 May 2015 23:09:39 +0200	[thread overview]
Message-ID: <1432156179.7907.3.camel@citrix.com> (raw)
In-Reply-To: <20150519173511.GT26335@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]

On Tue, 2015-05-19 at 18:35 +0100, Wei Liu wrote:
> On Sat, May 16, 2015 at 03:15:21AM +0200, Dario Faggioli wrote:

> > > === Hypervisor X86 === 
> > 
> > > *  HT enabled with credit has 7.9 per perf drop. (none)
> > >    kernbench demonstrated it
> > >    http://www.gossamer-threads.com/lists/xen/devel/339409
> > >    This has existed since credit1 introduction.
> > >   -  Dario Faggioli
> > >
> > Let me clarify this a bit.
> > 
> > First of all, let me point out that the issue only shows up in
> > under-loaded systems (i.e., with less active vcPUs then the host has
> > pCPUs). In any case, this is something inherent in Credit1 architecture,
> > and I don't have a sensible idea on how to deal with it without causing
> > other problems.
> > 
> > I am working on some improvement to Credit1 (e.g., introducing load
> > tracking and basing some decisions on it), which hopefully will help
> > better performance even in this case, but I'm not actively working on
> > fixing this (if it can be fixed).
> > 
> 
> I have moved this to deferred section. Is this OK?
> 
Sounds good, thanks.

Regards,
Dario

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2015-05-20 21:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  5:01 Xen 4.6 Development Update (four months reminder) wei.liu2
2015-05-13  5:17 ` Meng Xu
2015-05-13  5:56 ` Chun Yan Liu
2015-05-13  8:56   ` Tamas K Lengyel
2015-05-13  6:18 ` Status of VM event patches (Was: " Razvan Cojocaru
2015-05-13  7:04   ` Jan Beulich
2015-05-13  7:40     ` Razvan Cojocaru
2015-05-13  8:46 ` Yang Hongyang
2015-05-13  8:54 ` Status of ARM features (Was: Re: Xen 4.6 Development Update (four months reminder)) Julien Grall
2015-05-13  9:56 ` Status of soft reset for PVHVM (Was: " Vitaly Kuznetsov
2015-05-13 11:06 ` Xen 4.6 Development Update (four months reminder) Hu, Robert
2015-05-13 13:49 ` Daniel Kiper
2015-05-14 23:48 ` Status of VMware tools support (Was: Xen 4.6 Development Update (four months reminder)) Don Slutz
2015-05-15 10:38 ` Xen 4.6 Development Update (four months reminder) Ian Campbell
2015-05-16  0:42 ` Status of 'Credit2: hard and soft affinity; [Re: Xen 4.6 Development Update (four months reminder)] Dario Faggioli
2015-05-18  7:07   ` Justin Weaver
2015-05-16  1:15 ` Status of Credit2 and Credit1 [was: " Dario Faggioli
2015-05-19 17:35   ` Wei Liu
2015-05-20 21:09     ` Dario Faggioli [this message]

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=1432156179.7907.3.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jtweaver@hawaii.edu \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.