From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 3/3] xen: credit1: avoid boosting vCPUs being "just" migrated
Date: Thu, 11 Feb 2016 18:45:01 +0100 [thread overview]
Message-ID: <1455212701.3148.294.camel@citrix.com> (raw)
In-Reply-To: <56BC9B0502000078000D1087@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2087 bytes --]
On Thu, 2016-02-11 at 06:30 -0700, Jan Beulich wrote:
> > > > On 11.02.16 at 12:39, <dario.faggioli@citrix.com> wrote:
> > --- a/xen/common/sched_credit.c
> > +++ b/xen/common/sched_credit.c
> > @@ -1022,11 +1022,14 @@ csched_vcpu_wake(const struct scheduler
> > *ops, struct vcpu *vc, unsigned wf)
> > * more CPU resource intensive VCPUs without impacting
> > overall
> > * system fairness.
> > *
> > - * The one exception is for VCPUs of capped domains unpausing
> > - * after earning credits they had overspent. We don't boost
> > - * those.
> > + * There are a couple of exceptions, when we don't want to
> > boost:
> > + * - VCPUs that are waking up after a migration, rather than
> > + * after having block;
> > + * - VCPUs of capped domains unpausing after earning credits
> > + * they had overspent.
> > */
> > - if ( svc->pri == CSCHED_PRI_TS_UNDER &&
> > + if ( !(wf & WF_migrated) &&
> > + svc->pri == CSCHED_PRI_TS_UNDER &&
> > !test_bit(CSCHED_FLAG_VCPU_PARKED, &svc->flags) )
> > {
>
> Considering the other svc->flags check done here, wouldn't it be
> possible to achieve the same effect without patch 2, by having
> csched_cpu_pick() set a newly defined flag, and check for it here?
>
It can indeed. I've coded it up, and I like the way it came out better.
I'm rerunning the benchmarks right now (just in case! :-)). I'll send
v2 out as soon as they finish.
I did like the idea of "wakeup flags", and I think they may actually
turn out useful, but they're not necessary for this specific use case,
as it appears. Well, next time. ;-)
Thanks and 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
prev parent reply other threads:[~2016-02-11 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 11:38 [PATCH 0/3] xen: sched: Credit1 shouldn't boost vcpus being migrated Dario Faggioli
2016-02-11 11:38 ` [PATCH 1/3] xen: credit1: trace vCPU boost/unboost Dario Faggioli
2016-02-11 11:38 ` [PATCH 2/3] xen: sched: add wakeup flags to the scheduler interface Dario Faggioli
2016-02-11 13:24 ` Jan Beulich
2016-02-11 17:46 ` Dario Faggioli
2016-02-11 11:39 ` [PATCH 3/3] xen: credit1: avoid boosting vCPUs being "just" migrated Dario Faggioli
2016-02-11 13:30 ` Jan Beulich
2016-02-11 17:45 ` 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=1455212701.3148.294.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.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).