From: Dario Faggioli <raistlin@linux.it>
To: "Lv, Hui" <hui.lv@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir (Xen.org)" <keir@xen.org>,
George Dunlap <George.Dunlap@eu.citrix.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
George Dunlap <george.dunlap@citrix.com>,
"Duan, Jiangang" <jiangang.duan@intel.com>
Subject: RE: [PATCH] scheduler rate controller
Date: Mon, 31 Oct 2011 11:16:36 +0100 [thread overview]
Message-ID: <1320056196.15109.34.camel@Abyss> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F34B3905D03@shsmsx502.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2193 bytes --]
On Sat, 2011-10-29 at 10:05 +0800, Lv, Hui wrote:
> As you said, if applying the seveal_ms_delay, it will happen whenever system is normal or not (excessive frequency). It may possible have the consequence that 1)under normal condition, it will produce worse Qos than that without applying such delay, 2) under excessive frequency condition, the mitigation effect of 1ms-delay may be too weak. In addition, your idea is to delay scheduling instead of reducing, which means the total number of scheduling would probably not change.
>
I think it would. I mean, all the interrupts that arrive (and that are
causing TASKLET_SCHEDULE->schedule() right now) and see current vcpu not
having run for 1ms would collapse in just one call to schedule() at the
end of the 1ms delay from the time instant when the very first one
(interrupt) happened... Isn't it?
If yes, that would definitely reduce the number of calls to schedule().
> I think one possible solution, is to make the value of 1ms-delay adaptive according to the system status (low load or high load). If so, SRC patch just covered the excessive condition currently :). That's why I mentioned to treat normal and excessive conditions separately and don't influence the normal case as much as possible. Because we never know the consequence without amount of testing work. :)
>
Well, again, from my perspective, these numbers (1ms, 10ms) really looks
like ages, considering for example audio processing workloads with
software like JACK needs periodicity of 1.3 or 2.6 ms, and thus having
1ms or (for worse) 10ms eaten by the scheduler would definitely step on
their toes. I understand we're not talking very much about audio
processing VMs here but hey, if it has to be general purpose... :-P
> Some of my stupid thinking :)
>
Same for mine. :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-10-31 10:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 3:36 [PATCH] scheduler rate controller Lv, Hui
2011-10-24 16:17 ` George Dunlap
2011-10-24 16:57 ` Keir Fraser
2011-10-24 21:20 ` Dario Faggioli
2011-10-25 7:57 ` Dario Faggioli
2011-10-28 2:07 ` Lv, Hui
2011-10-28 8:10 ` Dario Faggioli
2011-10-28 8:52 ` Lv, Hui
2011-10-28 10:09 ` Dario Faggioli
2011-10-28 16:18 ` George Dunlap
2011-10-29 2:05 ` Lv, Hui
2011-10-31 10:16 ` Dario Faggioli [this message]
2011-11-03 4:28 ` George Dunlap
2011-11-04 14:08 ` Lv, Hui
2011-11-14 15:22 ` George Dunlap
2011-11-14 15:30 ` George Dunlap
2011-11-28 17:31 ` Lv, Hui
2011-12-01 17:13 ` George Dunlap
2011-12-11 15:27 ` Lv, Hui
2011-12-12 11:43 ` George Dunlap
2011-12-13 2:24 ` Lv, Hui
2011-10-31 9:59 ` Dario Faggioli
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=1320056196.15109.34.camel@Abyss \
--to=raistlin@linux.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=eddie.dong@intel.com \
--cc=george.dunlap@citrix.com \
--cc=hui.lv@intel.com \
--cc=jiangang.duan@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.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.