xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sisu Xi <xisisu@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Robert VanVossen <robert.vanvossen@dornerworks.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Joshua Whitehead <josh.whitehead@dornerworks.com>,
	Chong Lee <lichong659@gmail.com>, Meng Xu <xumengpanda@gmail.com>,
	Nate Studer <nate.studer@dornerworks.com>
Subject: Re: [RFC Patch 1/3] Remove sedf extra, weight, and latency parameter support.
Date: Fri, 21 Mar 2014 11:50:56 -0500	[thread overview]
Message-ID: <CAPqOm-oJaF7wzMNvUwHdNwkDxcZiVNfho4Lxe9DPXMS4avJVEQ@mail.gmail.com> (raw)
In-Reply-To: <1395418612.13892.155.camel@Solace>


[-- Attachment #1.1: Type: text/plain, Size: 2563 bytes --]

Hi, Dario:

Thanks for the coordination! It would be great if we can schedule a meeting
to discuss this.

I am widely open today, this weekend, and next Monday.
I am ccing Meng and Chong, who's my collaborator on the RT-Xen project to
see if they are interested in the meeting.

Thanks again and I look forward to talking to you!
Sisu


On Fri, Mar 21, 2014 at 11:16 AM, Dario Faggioli
<dario.faggioli@citrix.com>wrote:

> On ven, 2014-03-21 at 08:25 -0400, Nate Studer wrote:
> > On 3/21/2014 7:16 AM, Ian Campbell wrote:
>
> > > If you intend in a future non-RFC version of this series to do
> something
> > > like that then we can follow that path at that time.
> >
> > Thanks for the information Ian.
> >
> > This is the intention, so we would prefer the LIBXL_HAVE_NEW_SCHED_THING
> path.
> > It seems cleaner.
> >
> > We just wanted to make sure that there were no major objections to
> re-purposing
> > the sedf scheduler before we went too far down that path, and so far we
> have not
> > seen anybody step up to defend the sedf scheduler.
> >
> Well, TBH, seeing someone standing up to defend it as it is now would
> have been very surprising, from my point of view. :-)
>
> As I said, we really want something that is working, easier to maintain,
> extensible and more advanced, and I think you're putting efforts in the
> right direction" simplifying the current implementation is absolutely
> necessary, given its super-broken status.
>
> So, unless someone starts screaming really soon, I'd say "go ahead".
>
> The one thing I'd like to see, as I already said, is whether, once we'll
> have simplified it, and once it will get to enhance it (back), we could
> collaborate with the RT-Xen people.
>
> They already have an EDF scheduler which supports multiple budgetting
> algorithms, so I'm hoping that we can at least learn from their
> experience, if not (and let's see why not) borrow/upstream some of their
> code.
>
> If you think it would be useful, I'm up for setting up a call between
> me, you, Sisu, and everyone hat is interested. Just let me know.
>
> 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)
>
>


-- 
Sisu Xi, PhD Candidate

http://www.cse.wustl.edu/~xis/
Department of Computer Science and Engineering
Campus Box 1045
Washington University in St. Louis
One Brookings Drive
St. Louis, MO 63130

[-- Attachment #1.2: Type: text/html, Size: 3486 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2014-03-21 16:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 19:13 [RFC Patch 0/3] Putting the "Simple" back in sedf Nathan Studer
2014-03-14 19:13 ` [RFC Patch 1/3] Remove sedf extra, weight, and latency parameter support Nathan Studer
2014-03-17  8:13   ` Jan Beulich
2014-03-17 17:02   ` Dario Faggioli
2014-03-21 11:16   ` Ian Campbell
2014-03-21 12:25     ` Nate Studer
2014-03-21 16:16       ` Dario Faggioli
2014-03-21 16:50         ` Sisu Xi [this message]
2014-03-24 15:44           ` Dario Faggioli
2014-03-14 19:13 ` [RFC Patch 2/3] Remove extra queues, latency scaling, and weight support from sedf Nathan Studer
2014-03-14 19:13 ` [RFC Patch 3/3] Fix formatting and misleading comments/variables in sedf Nathan Studer
2014-03-17 16:49   ` Dario Faggioli
2014-03-17 17:00     ` Nate Studer
2014-03-14 19:22 ` [RFC Patch 0/3] Putting the "Simple" back " George Dunlap
2014-03-14 20:13   ` Nate Studer
2014-03-14 20:31     ` Nate Studer
2014-03-17 10:29       ` Dario Faggioli
2014-03-17 15:51     ` Dario Faggioli
2014-03-17 17:01       ` Sisu Xi

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=CAPqOm-oJaF7wzMNvUwHdNwkDxcZiVNfho4Lxe9DPXMS4avJVEQ@mail.gmail.com \
    --to=xisisu@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=josh.whitehead@dornerworks.com \
    --cc=lichong659@gmail.com \
    --cc=nate.studer@dornerworks.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).