All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Steinhaus <hsteinhaus@gmx.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: realtime scheduling
Date: Mon, 08 Aug 2005 23:11:03 +0200	[thread overview]
Message-ID: <42F7CA67.8000901@gmx.de> (raw)
In-Reply-To: <42F79359.8050900@cam.ac.uk>


>The default compile of the sedf scheduler is not optimised for latency
>(but the standard setting might work well...).
>You can do a couple of things:
>  -set the period of dom0 to roughly your latency (better half of it)
>and scale your slice accordingly
>   (e.g. 2ms period, 0.3ms slice...)
>  
>
Ok, done. I installed a fresh devel version of Xen (from Aug 7), 
including kernel 2.6.12.3 and SEDF scheduling (in my original post: Xen 
2.0.7, kernel 2.6.11.12, original scheduler). The major change: now the 
buffer problems even occur without any user domain.

I tried to play around with the period/slice parameters, and found some 
values that really boost the problems. As the HFC driver generates 8000 
interupts per second (I assume for timing purposes), the desired period 
of 62500 ns is not possible on my machine. I think, I'll take a closer 
look on the driver first...


>  -or edit xen/common/schedule_sedf.c and change
>     #define UNBLOCK UNBLOCK_EXTRA_SUPPORT
>     to
>     #define UNBLOCK UNBLOCK_ATROPOS
>     and then set the appropriate latancy value in xm sedf (this does
>exactly the same thing internaly
>  
>
Makes no recognizable difference, in my opinion.

Thanks,
  Holger

  reply	other threads:[~2005-08-08 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 15:06 realtime scheduling Holger Steinhaus
2005-08-08 15:25 ` Keir Fraser
2005-08-08 17:16   ` Stephan Diestelhorst
2005-08-08 21:11     ` Holger Steinhaus [this message]
2005-08-09  7:27       ` Keir Fraser

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=42F7CA67.8000901@gmx.de \
    --to=hsteinhaus@gmx.de \
    --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.