xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	xen-devel@lists.xenproject.org,
	Anshul Makkar <anshul.makkar@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [for-4.8 PATCH] xen: credit2: make runqueues be per-socket by default.
Date: Tue, 29 Nov 2016 11:14:25 +0000	[thread overview]
Message-ID: <20161129111425.GS11640@citrix.com> (raw)
In-Reply-To: <148041702351.16498.17129591426095525570.stgit@Solace.fritz.box>

On Tue, Nov 29, 2016 at 11:57:03AM +0100, Dario Faggioli wrote:
> Benchmarks have shown that per-socket runqueues arrangement
> behaves better (e.g., we achieve better load balancing)
> than the current per-core default.
> 
> Here's an example (coming from
> https://lists.xen.org/archives/html/xen-devel/2016-06/msg02287.html ):
> 
> |=======================================|
> | XEN BUILD TIME, LOW LOAD, NO NOISE    |
> |---------------------------------------|
> |       runq=core   runq=socket         |
> |         35.200       33.433           |
> |---------------------------------------|------------------------------|
> | XEN BUILD TIME, HIGH LOAD, NO NOISE   | IPERF, HIGH LOAD, NO NOISE   |
> |---------------------------------------|------------------------------|
> |       runq=core   runq=socket         |     runq=core runq=socket    |
> |         18.013       18.530           |       23.200     23.466      |
> |---------------------------------------|------------------------------|
> | XEN BUILD TIME, LOW LOAD, WITH NOISE  |
> |-------------------------------------  |
> |       runq=core   runq=socket         |
> |         45.866       39.493           |
> |---------------------------------------|------------------------------|
> | XEN BUILD TIME, HIGH LOAD, WITH NOISE | IPERF, HIGH LOAD, WITH NOISE |
> |---------------------------------------|------------------------------|
> |       runq=core   runq=socket         |     runq=core runq=socket    |
> |         36.840       29.080           |       19.967     21.000      |
> |=======================================|==============================|
> 
> The only reason why we went for per-core, initially, was to
> introduce some form of hyperthreading support. Now we have
> hyperthreading support, independently from how runqueues
> are organized (9bb9c7388 "xen: credit2: implement true SMT
> support"), and thus we can switch to per-socket.
> 
> Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
> ---
> Cc: Anshul Makkar <anshul.makkar@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
> ---
> George's Ack obtained 'out of band', as he is away.
> ---

Strictly speaking, this is not necessary for 4.8 because even though the
default configuration is not optimal, there is a simple way to change
it.

On the other hand, because credit2 is declared supported in this
release, it is better to have a sensible default setting for credit2.

The risk is that changing the default value would cause osstest to
discover bugs in the scheduler logic, hence blocking the release. But
overall I think the chance is low, but Dario can you please state to
what extend did you test this patch?

Wei.

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

  reply	other threads:[~2016-11-29 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 10:56 [for-4.8 PATCH] xen: credit2: make runqueues be per-socket by default Dario Faggioli
2016-11-29 10:57 ` Dario Faggioli
2016-11-29 11:14   ` Wei Liu [this message]
2016-11-29 11:33     ` Dario Faggioli
2016-11-29 11:42       ` Wei Liu
2016-11-29 11:51         ` Jan Beulich
2016-11-29 11:57           ` Dario Faggioli
2016-11-29 12:01           ` Wei Liu

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=20161129111425.GS11640@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=anshul.makkar@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.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).