From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
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: Load calculation refresh in credit2 (was in Re: Questions about the use of idle_vcpu[])
Date: Tue, 19 Jan 2016 10:23:35 +0100 [thread overview]
Message-ID: <1453195415.11427.119.camel@citrix.com> (raw)
In-Reply-To: <569CF2B8.9020406@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]
On Mon, 2016-01-18 at 14:12 +0000, George Dunlap wrote:
> [Changing the title to align with the current topic]
>
> Load balancing only happens on a reset event; and the frequency of
> reset
> events will be CREDIT_INIT / (% utilization); so for a system at 1%
> utilization that would be once every second. Is that the kind of
> number
> you were seeing? Or were you actually seeing idle runqueues not
> having
> anything pushed to them *during* a balance for some reason?
>
As I said, I need to recheck... but yes, this could be the cause of my
"issue".
In fact, since I was reading the load from the toolstack (that was one
of the purposes of the whole thing), it's quite likely that I was
seeing non-updated values because the load balance hadn't run since a
while.
I'll keep this in mind when revisiting that work, and try to cook a
patch that avoid setting the timer when the idle vcpu is returned, and
see how it goes.
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-19 9:23 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
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 [this message]
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=1453195415.11427.119.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=george.dunlap@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.