xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Meng Xu <mengxu@cis.upenn.edu>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Design RFC] Towards work-conserving RTDS scheduler
Date: Thu, 18 Aug 2016 11:07:05 -0400	[thread overview]
Message-ID: <CAENZ-+=6Q71Y29-4zCTxoVO16Sw3W_RBLSxHBAWLwmkL5fRCJw@mail.gmail.com> (raw)
In-Reply-To: <1471515726.6806.72.camel@citrix.com>

On Thu, Aug 18, 2016 at 6:22 AM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On Tue, 2016-08-09 at 09:57 -0400, Meng Xu wrote:
>> On Mon, Aug 8, 2016 at 5:38 AM, Dario Faggioli
>> <dario.faggioli@citrix.com> wrote:
>> >
>> > I'm just thinking out loud and
>> > wondering:
>> >  - could it be useful to have a scheduling analysis in place for
>> > the
>> >    scheduler in work conserving mode (one, of course, that takes
>> > into
>> >    account and give guarantees on the otherwise idle bandwidth... I
>> >    know that the existing one holds! :-P) ?
>> >  - if yes, do you already have one --or do you think it will be
>> >    possible to develop one-- for your priority-index based model?
>> I think I could potentially develop one such analysis.
>>
> Great. Let me know if you need any help writing the paper! :-P

Sure, I definitely will. :-D
I'm in the middle of another work. I need to do some survey on the
literatures (such as the ones you mentioned) about the work-conserving
real-time scheduling. The ideal goal in my mind is to have the
scheduler become work-conserving, and we can have a paper as a "side
product".  ;-)

Thanks and best regards,

Meng

-- 
------------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-08-18 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04  5:15 [Design RFC] Towards work-conserving RTDS scheduler Meng Xu
2016-08-08  9:38 ` Dario Faggioli
2016-08-09 13:57   ` Meng Xu
2016-08-18 10:22     ` Dario Faggioli
2016-08-18 15:07       ` Meng Xu [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='CAENZ-+=6Q71Y29-4zCTxoVO16Sw3W_RBLSxHBAWLwmkL5fRCJw@mail.gmail.com' \
    --to=mengxu@cis.upenn.edu \
    --cc=dario.faggioli@citrix.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).