From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Anshul Makkar <anshul.makkar@citrix.com>
Subject: Re: [for-4.8 PATCH] xen: credit2: make runqueues be per-socket by default.
Date: Tue, 29 Nov 2016 12:33:24 +0100 [thread overview]
Message-ID: <1480419204.3178.36.camel@citrix.com> (raw)
In-Reply-To: <20161129111425.GS11640@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1718 bytes --]
On Tue, 2016-11-29 at 11:14 +0000, Wei Liu wrote:
> On Tue, Nov 29, 2016 at 11:57:03AM +0100, Dario Faggioli wrote:
> 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.
>
Absolutely true.
> On the other hand, because credit2 is declared supported in this
> release, it is better to have a sensible default setting for credit2.
>
Exactly.
> 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?
>
I've tried to state that in the cover letter:
https://lists.xen.org/archives/html/xen-devel/2016-11/msg02616.html
In some more details, it is _months_ that I and Anshul run benchmarks
with Credit2 running in this configuration.
It's months that, all the time that I boot my test box, either to do
Credit2 related development and testing, or completely unrelated things
(e.g., recently, when testing the new Fedora 25 as HVM and PV guest), I
use Credit2 in this configuration.
George has done some runs of his schedbench suite with this
configuration (to compare Credit1 vs Credit2 per-core vs Credit2 per-
socket).
So, if you ask me "how much is this tested", my answer would be "really
really really a lot". :-)
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
next prev parent reply other threads:[~2016-11-29 11:33 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
2016-11-29 11:33 ` Dario Faggioli [this message]
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=1480419204.3178.36.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--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 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).