From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
george.dunlap@eu.citrix.com, joao.m.martins@oracle.com,
boris.ostrovsky@oracle.com, xen-devel@lists.xen.org
Subject: Re: schedulers and topology exposing questions
Date: Thu, 28 Jan 2016 09:55:45 +0000 [thread overview]
Message-ID: <1453974945.26691.10.camel@citrix.com> (raw)
In-Reply-To: <56A8E802.9090702@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
On Wed, 2016-01-27 at 15:53 +0000, George Dunlap wrote:
> On 27/01/16 15:27, Konrad Rzeszutek Wilk wrote:
> >
> > So Elena started looking at the CPU bound and seeing how Xen
> > behaves then
> > and if we can improve the floating situation as she saw some
> > abnormal
> > behavious.
>
> OK -- if the focus was on the two cases where the Xen credit1
> scheduler
> (apparently) co-located two cpu-burning vcpus on sibling threads,
> then
> yeah, that's behavior we should probably try to get to the bottom of.
>
Well, let's see the trace.
In any case, I'm up to trying hooking the SMT load balancer in
runq_tickle (which would mean doing it upon every vcpus wakeup).
My gut feeling is that the overhead my outwieght the benefit, and that
it will actually reveal useful only in a minority of the
cases/workloads, but it's maybe worth a try.
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: 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
next prev parent reply other threads:[~2016-01-28 9:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:54 schedulers and topology exposing questions Elena Ufimtseva
2016-01-22 17:29 ` Dario Faggioli
2016-01-22 23:58 ` Elena Ufimtseva
2016-01-26 11:21 ` George Dunlap
2016-01-27 14:25 ` Dario Faggioli
2016-01-27 14:33 ` Konrad Rzeszutek Wilk
2016-01-27 15:10 ` George Dunlap
2016-01-27 15:27 ` Konrad Rzeszutek Wilk
2016-01-27 15:53 ` George Dunlap
2016-01-27 16:12 ` Konrad Rzeszutek Wilk
2016-01-28 9:55 ` Dario Faggioli [this message]
2016-01-29 21:59 ` Elena Ufimtseva
2016-02-02 11:58 ` Dario Faggioli
2016-01-27 16:03 ` Elena Ufimtseva
2016-01-28 9:46 ` Dario Faggioli
2016-01-29 16:09 ` Elena Ufimtseva
2016-01-28 15:10 ` Dario Faggioli
2016-01-29 3:27 ` Konrad Rzeszutek Wilk
2016-02-02 11:45 ` Dario Faggioli
2016-02-03 18:05 ` Konrad Rzeszutek Wilk
2016-01-27 14:01 ` Dario Faggioli
2016-01-28 18:51 ` Elena Ufimtseva
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=1453974945.26691.10.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=joao.m.martins@oracle.com \
--cc=konrad.wilk@oracle.com \
--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).