From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xenproject.org, George Dunlap <george.dunlap@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>
Subject: Re: [PATCH 0/6] xen: sched: improve scalability of Credit1, and optimize a bit both Credit1 and Credit2
Date: Mon, 27 Mar 2017 11:08:36 +0200 [thread overview]
Message-ID: <1490605716.25397.1.camel@citrix.com> (raw)
In-Reply-To: <148844531279.23452.17528540110704914171.stgit@Solace.fritz.box>
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
On Thu, 2017-03-02 at 11:37 +0100, Dario Faggioli wrote:
> Hello,
>
Hey, George,
About this series. I was re-looking at it, and I figured out that:
> Dario Faggioli (6):
> xen: credit1: simplify csched_runq_steal() a little bit.
> xen: credit: (micro) optimize csched_runq_steal().
> xen: credit1: increase efficiency and scalability of load
> balancing.
>
Here in patch 3, overhead inside __runq_insert() and __runq_remove()
can be reduced.
> xen: credit1: treat pCPUs more evenly during balancing.
>
And about patch 4, I like it, but I'm currently running more benchmarks
to make sure of its impact, and its cost-vs-benefit ratio.
I will send a v2 shortly, so, maybe, if you're in desperate look for
reviewing something from me, feel free to skip (or just quickly glance
at) this series. :-)
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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-27 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 10:37 [PATCH 0/6] xen: sched: improve scalability of Credit1, and optimize a bit both Credit1 and Credit2 Dario Faggioli
2017-03-02 10:38 ` [PATCH 1/6] xen: credit1: simplify csched_runq_steal() a little bit Dario Faggioli
2017-03-03 9:35 ` anshul makkar
2017-03-03 13:39 ` Dario Faggioli
2017-03-02 10:38 ` [PATCH 2/6] xen: credit: (micro) optimize csched_runq_steal() Dario Faggioli
2017-03-03 9:48 ` anshul makkar
2017-03-03 13:53 ` Dario Faggioli
2017-03-02 10:38 ` [PATCH 3/6] xen: credit1: increase efficiency and scalability of load balancing Dario Faggioli
2017-03-02 11:06 ` Andrew Cooper
2017-03-02 11:35 ` Dario Faggioli
2017-04-06 7:37 ` Dario Faggioli
2017-03-02 10:38 ` [PATCH 4/6] xen: credit1: treat pCPUs more evenly during balancing Dario Faggioli
2017-03-02 10:38 ` [PATCH 5/6] xen/tools: tracing: add record for credit1 runqueue stealing Dario Faggioli
2017-03-02 10:38 ` [PATCH 6/6] xen: credit2: avoid cpumask_any() in pick_cpu() Dario Faggioli
2017-03-02 10:58 ` [PATCH 0/6] xen: sched: improve scalability of Credit1, and optimize a bit both Credit1 and Credit2 Dario Faggioli
2017-03-27 9:08 ` 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=1490605716.25397.1.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=george.dunlap@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 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).