From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Tianyang Chen <tiche@seas.upenn.edu>,
Meng Xu <xumengpanda@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Questions about the use of idle_vcpu[]
Date: Mon, 18 Jan 2016 13:47:29 +0100 [thread overview]
Message-ID: <1453121249.11427.83.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZYHR2S4xF=fpitPbNKRv=SMa35JM1fSJAXkzkqYS2vXXw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1845 bytes --]
On Mon, 2016-01-18 at 12:37 +0000, George Dunlap wrote:
> On Mon, Jan 18, 2016 at 11:00 AM, Dario Faggioli
> <dario.faggioli@citrix.com> wrote:
> > >
> > Credit2, AFAICR, could also avoid _always_ re-setting the timer,
> > but it
> > does need to do that at least a few times, even when idle is
> > selected,
> > because of the dynamic load tracking mechanism it includes. In
> > fact,
> > that is based on a 'decaying average', which in turns relies on
> > csched2_schedule() to run and update the statistics, even when the
> > cpu
> > is idle. If we don't do that, the load tracking mechanism will
> > never
> > see that the cpu (well, it's actually the runqueue) is idle, and
> > the
> > load will never go down! :-/
>
> I don't think that's true -- it looks like balance_load() will call
> __update_runq_load() on the "other" runqueue before considering it,
> and will also call __update_svc_load() on each vcpu before
> considering
> it. Shouldn't that suffice?
>
Mm... It looks like it should.
And yet, I observed that 'load not going down' behavior while doing
development for the patch I mentioned, both on Credit2 and Credit (with
patches for extending the load tracking to Credit applied).
I was, in the same series, also trying to optimize the Credit2's load
balancer a little bit, though, so what I saw may be the effect of some
other change of mine...
I'll have a go at just disabling the periodic scheduler activation when
cpu is idle in the current code, and if it works, I'll send a patch.
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
next prev parent reply other threads:[~2016-01-18 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 1:04 Questions about the use of idle_vcpu[] Tianyang Chen
2016-01-18 10:47 ` George Dunlap
2016-01-18 11:00 ` Dario Faggioli
2016-01-18 12:37 ` George Dunlap
2016-01-18 12:47 ` Dario Faggioli [this message]
2016-01-18 14:12 ` Load calculation refresh in credit2 (was in Re: Questions about the use of idle_vcpu[]) George Dunlap
2016-01-19 9:23 ` Dario Faggioli
2016-01-18 16:07 ` Questions about the use of idle_vcpu[] Meng Xu
2016-01-18 16:32 ` Dario Faggioli
2016-01-18 16:41 ` Meng Xu
2016-01-19 22:59 ` Tianyang Chen
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=1453121249.11427.83.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=tiche@seas.upenn.edu \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.