From: Dario Faggioli <dario.faggioli@citrix.com>
To: Nate Studer <nate.studer@dornerworks.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Xi Sisu <xisisu@gmail.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@lists.xen.org, josh.whitehead@dornerworks.com
Subject: Re: [RFC Patch 0/3] Putting the "Simple" back in sedf.
Date: Mon, 17 Mar 2014 11:29:52 +0100 [thread overview]
Message-ID: <1395052192.4159.257.camel@Solace> (raw)
In-Reply-To: <53236731.4060702@dornerworks.com>
[-- Attachment #1.1: Type: text/plain, Size: 1079 bytes --]
On ven, 2014-03-14 at 16:31 -0400, Nate Studer wrote:
> > In the long term, a more extensible version of Dario's favorite scheduler, CBS
> > (Constant Bandwidth Server): a selectable budgeting algorithm that sets vcpu
> > deadlines with the sedf scheduler on the backend scheduling the vcpu with the
> > earliest deadline. Preferably it would support other budgeting algorithms as
> > well such as Total Bandwidth Server, etc...
>
> Speaking of Dario, I got his e-mail address wrong. My apologies.
>
> CC'ing his correct address.
>
Hey, no problem... I saw it on the list, I saw my name there, but did
not notice the address, and was wondering why I did not get my own
copy! :-P
Sorry I haven't replied yet, I was otherwise engaged, but I'm on it
right now! :-P
Thanks and 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: 198 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:[~2014-03-17 10:29 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
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 [this message]
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=1395052192.4159.257.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=josh.whitehead@dornerworks.com \
--cc=nate.studer@dornerworks.com \
--cc=robert.vanvossen@dornerworks.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@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).