Re: [Xen-devel] [PATCH v2] Modified RTDS scheduler to use an event-driven model instead of polling.

[Meng Xu <xumengpanda@xxxxxxxxx>]

[Dario was forgotten in this email. Adding him back..:-( ]



2015-06-27 12:53 GMT-07:00 Dagaen Golomb <dgolomb@xxxxxxxxxxxxxx>:
> All,
>
> Sorry for the repeated send to the mailing list, I forgot to add some
> cc's and wanted to make sure
> everyone was included.
>
> This is the new patch that works towards how Dario suggested
> structuring the event-driven move.
> It uses the previous timer to drive the rt_schedule function, which
> enforces budget depletions and
> performs scheduling decisions.

This is more like a cover letter. Next time, can you use the option
--compose to send a cover letter with the detailed design along with
the patch?

You can also link to the discusssion we had about the design.

>
> There is an added timer that only handles replenishments, which is
> called at the time the next
> replenishment will occur. To do this, we now also keep the depletedq
> sorted. If it detects it has
> moved a vCPU into the first [# CPUs] slots in the runq, it tickles the
> runq with the added vCPU.
> If the depletedq becomes empty the timer is stopped, and if the
> scheduler moves a vCPU into
> a previously empty depletedq it restarts the timer.
>
> This may have some issues with corner cases that were discussed
> earlier, such as unexpected
> behavior if the two timers are armed for the same time. It should be
> correct for the common case.

Could you elaborate more about when two timers can be armed for the same time?

Thanks,

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@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel