Re: Sched planning: Ideal scheduler, and credit1

[Gaurav Somani <onlineengineer@gmail.com>]

Hi George,

had a great and quite illustrative read. having some queries?



* Credit1, and why it doesn't work well for video

At a basic level, credit1 has two main priorities: UNDER and OVER.

 Credits are handed out every 30ms according to weight.  VMs that have
positive credits are classed at priority UNDER, and those with
negative credits are classed as OVER..............


>>> I have read in ongaro et al's (Schedulin I/O in Virtual machine
>>> monitors) paper that credits are handed over to domains after the sum of
>>> all the credits in the system goes negative. So that time will come
>>> after all the UNDER and BOOST domains complete their execution for the
>>> all credit time=30ms they have.



Credit1 has a strong probabilistic element.  Every 10ms a "tick" timer
fires.  When the tick happens, a full 10ms of credit is subtracted
from the currently running VM.  It relies on an element of randomness
to spread this charge appropriately over all active VMs.

However, if we divide credits over all VMs we have the following
problem: if some VMs are idle, then what will happen is that the
"active" VMs will spend most of their time in the "OVER" state, while
mostly idle VMs will spend all of their time in the "UNDER" state
accumulating more and more credits.  So credit1 attempts to
distinguish between two kinds of workloads:

* "active" workloads, which are competing for CPU, and need to have
  credit accounting done.

* "inactive" workloads, which use minimal cpu, and need no credit
  accounting.




>>>>>>How credit scheduler can identify the application it is running at
very first time. Please correct me if i m wrong. Where does credit scheduler
classify active and inactive workload? (in code)


The rules for determining whether a VM was "active" or "inactive" are
as follows:

Thanks
Gaurav Somani
-- 
View this message in context: http://www.nabble.com/Sched-planning%3A-Ideal-scheduler%2C-and-credit1-tp23885657p23913205.html
Sent from the Xen - Dev mailing list archive at Nabble.com.