All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Diestelhorst <sd386@cam.ac.uk>
To: Tim Freeman <tfreeman@mcs.anl.gov>, xen-devel@lists.xensource.com
Subject: Re: sedf internals question
Date: Wed, 05 Apr 2006 15:34:49 +0200	[thread overview]
Message-ID: <4433C779.3070900@cam.ac.uk> (raw)
In-Reply-To: <20060312113307.2b0e584b.tfreeman@mcs.anl.gov>

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

  reply	other threads:[~2006-04-05 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-12 17:33 sedf internals question Tim Freeman
2006-04-05 13:34 ` Stephan Diestelhorst [this message]
2009-06-17 13:05   ` Gaurav Somani

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=4433C779.3070900@cam.ac.uk \
    --to=sd386@cam.ac.uk \
    --cc=tfreeman@mcs.anl.gov \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.