WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] sedf internals question

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] sedf internals question
From: Gaurav Somani <onlineengineer@xxxxxxxxx>
Date: Wed, 17 Jun 2009 06:05:29 -0700 (PDT)
Delivery-date: Wed, 17 Jun 2009 06:05:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4433C779.3070900@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060312113307.2b0e584b.tfreeman@xxxxxxxxxxx> <4433C779.3070900@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dear Stephen,

I want to know the importance of the extra command line field in sedf
scheduler. which is l (latency). It only says about when  domain does high
I/O work. What does it mean by "high"?
please give me the way. It will elp me in my research.

Thanks 
Gaurav
onlineengineerATgmailDOTcom



Stephan Diestelhorst-2 wrote:
> 
> Hi Tim,
> 
>>With SEDF, let us say a domain has a certain timeslice allocated to it
(say, 500 units) for a certain period (say 1000).  It runs for 200, then
blocks.  When it has become unblocked, the domain is put on the runqueue --
but say we are at the end of the period, maybe 900 units in.  Even if it
immediately runs for 100 units, what happens to the extra 200 units it is
guaranteed? 
>>  
>>
> Those guaranteed 500 units get binned once a domain blocks, because, as 
> you already pointed out, the scheduler can't make anymore guarantees at 
> that point. It can however give some of the suddenly available idle-time 
> to the domain. This is done by a priority scheme that supports those 
> domains most, that lost most of their time due to blocking. There are 
> (or used to be?) some different approaches in sched_sedf.c, which are 
> selectable at compile-time by exchanging macros. Play with those if you 
> want to tweak your system, although my measurements suggested the one 
> that is curently used to be the most useful. (And please send me some of 
> your results if you do ;-) )
> 
> Cheers,
>   Stephan
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/sedf-internals-question-tp3366114p24073256.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] sedf internals question, Gaurav Somani <=