From: Meng Xu <xumengpanda@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
Matt Wilson <msw@amazon.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"dongxiao.xu@intel.com" <dongxiao.xu@intel.com>,
"mengxu@cis.upenn.edu" <mengxu@cis.upenn.edu>,
"feng.wu@intel.com" <feng.wu@intel.com>,
"zhigang.x.wang@oracle.com" <zhigang.x.wang@oracle.com>,
Parth Dixit <parth.dixit@linaro.org>,
"Paul.Skentzos@dornerworks.com" <Paul.Skentzos@dornerworks.com>,
"wency@cn.fujitsu.com" <wency@cn.fujitsu.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
"guijianfeng@cn.fujitsu.com" <guijianfeng@cn.fujitsu.com>,
"Vijaya.Kumar@caviumnetworks.com"
<Vijaya.Kumar@caviumnetworks.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Joshua Whitehead <josh.whitehead@dornerworks.com>,
"zoltan.kiss@citrix.com" <zoltan.kiss@citrix.com>,
Arianna Avanzini <avanzini.arianna@gmail.com>,
"yang.z.zhang@intel.com" <yan>
Subject: Re: Xen 4.5 development update (July update)
Date: Wed, 20 Aug 2014 09:40:36 -0400 [thread overview]
Message-ID: <CAENZ-+nZxDkkTGPRxtbSFN6g1fhsrR6xmNoDMSWKXcreQ-VVdg@mail.gmail.com> (raw)
In-Reply-To: <1408528434.3725.82.camel@Solace.lan>
[-- Attachment #1.1: Type: text/plain, Size: 2128 bytes --]
Hi Dario,
> >
> > The "prognosis" is now the likelihood of completion in the 4.5
> > timeframe.
> > A bunch of items had moved to the completed phase which is
> > fantastic.
> >
> > none - nothing yet
> > fair - still working on it, patches are prototypes or RFC
> > ok - patches posted, acting on review
> > good - some last minute pieces
> > done - all done, might have bugs
> >
> >
> >
> > * XenRT (Preemptive Global Earliest Deadline First) (fair)
> > RFC patch posted (v2)
> > - Meng Xu
> >
>
> > Although it's a RFC patch, the XenRT can actually works well on the
> > machines we have. It currently has the preemptive global EDF
> > scheduler. The functionalities I'm currently working on is improving
> > its performance based on the review of the first version of patches.
> >
> If this is the case, I think you should drop the RFC tag/status.
>
> The idea is this: if you are asking the Xen dev community to provide
> some feedback on an idea/prototype implementation, then keep the RFC
> tag. If you are proposing something for inclusion in upstream Xen and,
> at least according to your own opinion, the code you are submitting is
> good enough to be included, then you need to drop the RFC tag.
>
> Then, of course, there will still be reviews, changes will be requested,
> new versions, etc., but it's important to mark the difference between
> these two phases, as said, by either retaining or dripping the tag.
>
> Basing on what you're saying (i.e., that you're working on performances
> optimizations), on how the last patch series looked and on the comments
> you got, I think it would be fine for you to send the next round of
> patches as proper v1, rather than "RFC v3", but that's, of course, up to
> you. :-)
>
Thank you very much for your advice! I will drop the RFC then in the next
round of patches (this week).
Best,
Meng
--
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
[-- Attachment #1.2: Type: text/html, Size: 3041 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-08-20 13:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 17:23 Xen 4.5 development update (July update) konrad.wilk
2014-08-15 17:58 ` Don Slutz
2014-08-15 19:40 ` Jan Beulich
2014-08-15 19:46 ` Konrad Rzeszutek Wilk
2014-08-15 21:19 ` Jan Beulich
2014-08-16 0:31 ` Meng Xu
2014-08-20 9:53 ` Dario Faggioli
2014-08-20 13:40 ` Meng Xu [this message]
2014-08-19 16:46 ` Dario Faggioli
2014-08-21 19:17 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2014-09-02 20:45 konrad.wilk
2014-09-02 21:25 ` Andrew Cooper
2014-09-03 10:09 ` Ian Campbell
2014-09-03 10:13 ` Wei Liu
2014-09-03 11:27 ` Andrew Cooper
2014-09-03 11:53 ` Shriram Rajagopalan
2014-09-03 11:58 ` Andrew Cooper
2014-09-03 19:54 ` Julien Grall
2014-09-09 14:04 ` Konrad Rzeszutek Wilk
2014-09-03 1:17 ` Hongyang Yang
2014-09-03 12:05 ` Shriram Rajagopalan
2014-09-03 1:23 ` Mukesh Rathor
2014-09-03 12:54 ` Boris Ostrovsky
2014-09-03 15:47 ` Tamas K Lengyel
2014-09-03 15:53 ` Roy Franz
2014-09-09 9:53 ` Ian Campbell
2014-09-09 10:30 ` Jan Beulich
2014-09-09 14:09 ` Konrad Rzeszutek Wilk
2014-09-09 14:30 ` Jan Beulich
2014-09-09 15:48 ` Konrad Rzeszutek Wilk
2014-09-09 14:06 ` Konrad Rzeszutek Wilk
2014-09-09 13:51 ` Meng Xu
2014-09-09 17:02 ` Dario Faggioli
2014-07-23 0:28 konrad.wilk
2014-07-23 0:47 ` Boris Ostrovsky
2014-07-23 16:09 ` Konrad Rzeszutek Wilk
2014-07-23 8:32 ` Andrew Cooper
2014-07-23 9:51 ` Ian Campbell
2014-07-23 10:20 ` Stefano Stabellini
2014-07-23 12:54 ` Don Slutz
2014-07-23 13:03 ` Stefano Stabellini
2014-07-23 18:34 ` Don Slutz
2014-07-24 11:21 ` Stefano Stabellini
2014-07-23 13:42 ` Fabio Fantoni
2014-07-23 13:45 ` Stefano Stabellini
2014-07-23 13:55 ` Fabio Fantoni
2014-07-23 17:02 ` Konrad Rzeszutek Wilk
2014-07-24 11:23 ` Stefano Stabellini
2014-07-25 17:22 ` Konrad Rzeszutek Wilk
2014-07-23 16:18 ` Konrad Rzeszutek Wilk
2014-07-23 16:43 ` Ian Campbell
2014-07-28 17:35 ` Dario Faggioli
2014-08-04 15:44 ` Konrad Rzeszutek Wilk
[not found] ` <1406569210.4038.28.camel@Solace>
[not found] ` <CAENZ-+=pABtLnOU1CE8nHYd48S0_pB4cggLz1zrqQq2V1pcA-w@mail.gmail.com>
2014-07-29 1:37 ` Meng Xu
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-+nZxDkkTGPRxtbSFN6g1fhsrR6xmNoDMSWKXcreQ-VVdg@mail.gmail.com \
--to=xumengpanda@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Paul.Skentzos@dornerworks.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=artem.mygaiev@globallogic.com \
--cc=avanzini.arianna@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=dongxiao.xu@intel.com \
--cc=feng.wu@intel.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=josh.whitehead@dornerworks.com \
--cc=mengxu@cis.upenn.edu \
--cc=msw@amazon.com \
--cc=parth.dixit@linaro.org \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=zhigang.x.wang@oracle.com \
--cc=zoltan.kiss@citrix.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).