From: Dario Faggioli <dario.faggioli@citrix.com>
To: "dgolomb@seas.upenn.edu" <dgolomb@seas.upenn.edu>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xisisu@gmail.com" <xisisu@gmail.com>,
"mengxu@cis.upenne.edu" <mengxu@cis.upenne.edu>,
Ian Jackson <Ian.Jackson@citrix.com>,
"chaowang@wustl.edu" <chaowang@wustl.edu>,
George Dunlap <George.Dunlap@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"sokolsky@cis.upenn.edu" <sokolsky@cis.upenn.edu>,
"linhphan@cis.upenn.edu" <linhphan@cis.upenn.edu>,
"xumengpanda@gmail.com" <xumengpanda@gmail.com>,
"cdgill@cse.wustl.edu" <cdgill@cse.wustl.edu>,
"lichong659@gmail.com" <lichong659@gmail.com>,
"lu.wustl@gmail.com" <lu.wustl@gmail.com>,
"lee@cis.upenn.edu" <lee@cis.upenn.edu>
Subject: Re: [RFC] More efficient RTDS scheduler for Xen 4.6
Date: Mon, 23 Feb 2015 14:50:12 +0000 [thread overview]
Message-ID: <1424703009.5819.23.camel@citrix.com> (raw)
In-Reply-To: <CALcuvTjymwDd=VS2C4=D2wMw5tt0Vosd=8kDkSQO3x6391XP_g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1504 bytes --]
On Sun, 2015-02-22 at 00:31 -0500, Dagaen Golomb wrote:
> Hello everyone,
>
Hello,
> I'd like to solicit comments on improvements to the RTDS scheduler for
> Xen 4.6.
>
My first comment is that I'm happy that you guys are working on
this! :-)
> [Motivation]
>
> This change will increase the efficiency of the scheduler by
> eliminating invocations when no scheduling decision will be made. The
> scheduler is currently ran every 1 millisecond. If no tasks have
> terminated or budgets been depleted/replenished since the last
> scheduling, no changes will be made. Due to this, the scheduler is
> currently called at times when no new action will be taken, wasting
> processing resources. With the vital role that the scheduler plays and
> the frequency at which it is invoked, this design shift is a
> relatively important improvement.
>
I don't have much to say about this: I'm the one that suggested to go
for this approach, and I still think it is a goog idea... Looking
forward to see it implemented.
The only possible problem that comes to my mind is the need for a lot of
timers. How many, it will depend on the actual implementation. Using
fewer timer(s) would mean less overhead, but more issues on the event
queue(s).
The only way, I think, we have is just to get down and implement one
solution and see how fast it runs, and whether there are
overhead/scalability issue s(and address them at that time, if it will
be the case).
Regards,
Dario
[-- 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:[~2015-02-23 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 5:31 [RFC] More efficient RTDS scheduler for Xen 4.6 Dagaen Golomb
2015-02-22 15:53 ` Meng Xu
2015-02-23 14:50 ` 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=1424703009.5819.23.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=cdgill@cse.wustl.edu \
--cc=chaowang@wustl.edu \
--cc=dgolomb@seas.upenn.edu \
--cc=lee@cis.upenn.edu \
--cc=lichong659@gmail.com \
--cc=linhphan@cis.upenn.edu \
--cc=lu.wustl@gmail.com \
--cc=mengxu@cis.upenne.edu \
--cc=sokolsky@cis.upenn.edu \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xisisu@gmail.com \
--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.