From: Meng Xu <mengxu@cis.upenn.edu>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Tianyang Chen <tiche@seas.upenn.edu>,
George Dunlap <george.dunlap@citrix.com>,
Dagaen Golomb <dgolomb@seas.upenn.edu>
Subject: Re: [PATCH v7]xen: sched: convert RTDS from time to event driven model
Date: Thu, 10 Mar 2016 19:33:27 -0500 [thread overview]
Message-ID: <CAENZ-+=WawDE7trjxxKW48WVyit1iwQVYy-jRGVefm=YP_TFeg@mail.gmail.com> (raw)
In-Reply-To: <1457653986.3102.530.camel@citrix.com>
[My bad, Dario, I somehow only sent to you my reply... I'm resending
to everyone.]
On Thu, Mar 10, 2016 at 6:53 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On Thu, 2016-03-10 at 13:08 -0500, Meng Xu wrote:
>> On Thu, Mar 10, 2016 at 11:43 AM, Dario Faggioli
>> <dario.faggioli@citrix.com> wrote:
>> >
>> I think the pseudo-code makes sense. I just need to add some more
>> logic into it to make it complete. It forgets to handle the runq.
>>
> You mean...
>> >
>> >
>> > ...
>> > LIST_HEAD(tmp_replq);
>> >
>> > list_for_each_safe(iter, tmp, replq)
>> > {
>> > svc = replq_elem(iter);
>> >
>> > if ( now < svc->cur_deadline )
>> > break;
>> >
>> > list_del(&svc->replq_elem);
>> > rt_update_deadline(now, svc);
>> > list_add(&svc->replq_elem, &tmp_replq);
>> /* if svc is on runq, we need to put it to the correct place
>> since its deadline changes. */
>> if( __vcpu_on_q(svc) )
>> {
>> /* put back to runq */
>> __q_remove(svc);
>> __runq_insert(ops, svc);
>>
> ...This?
Yes.
>
> Well, sure, this was being done in repl_handler() in Tianyang's v7
> already, and I never meant to say we shouldn't do that any longer.
>
> I actually did not include it in here, because it was obvious to me
> that it still was necessary, and it was probably ok to put it in either
> of the loops (while I wanted to highlight what we need to do in the
> first and what in the second).
>
>> > It may look a bit convoluted, all these list moving, but I do like
>> > the
>> > fact that is is super self-contained.
>> >
>> > How does that sound / What did I forget this time ? :-)
>> Besides we need to "resort" the runq if the to-be-replenished vcpu is
>> on the runq now. Besides that, I think it's good.
>>
> If by re-sorting you mean what you added above, sure thing.
>
Yes. Since we have reached to some agreement on this, we can work on
the v8 now. :-D
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
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-03-11 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 1:39 [PATCH v7]xen: sched: convert RTDS from time to event driven model Tianyang Chen
2016-03-09 4:33 ` Meng Xu
2016-03-09 15:46 ` Dario Faggioli
2016-03-10 4:00 ` Meng Xu
2016-03-10 10:38 ` Dario Faggioli
2016-03-10 15:28 ` Meng Xu
2016-03-10 16:43 ` Dario Faggioli
2016-03-10 18:08 ` Meng Xu
2016-03-10 23:53 ` Dario Faggioli
2016-03-11 0:33 ` 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-+=WawDE7trjxxKW48WVyit1iwQVYy-jRGVefm=YP_TFeg@mail.gmail.com' \
--to=mengxu@cis.upenn.edu \
--cc=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=george.dunlap@citrix.com \
--cc=tiche@seas.upenn.edu \
--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).