From: Stephan Diestelhorst <sd386@cam.ac.uk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Holger Steinhaus <hsteinhaus@gmx.de>
Subject: Re: realtime scheduling
Date: Mon, 08 Aug 2005 18:16:09 +0100 [thread overview]
Message-ID: <42F79359.8050900@cam.ac.uk> (raw)
In-Reply-To: <b76ab46006c2f7dff2d29900f1c60c70@cl.cam.ac.uk>
Keir Fraser schrieb:
>
> On 8 Aug 2005, at 16:06, Holger Steinhaus wrote:
>
>> 1.) Are there any releases with a working RT-like scheduler?
>> 2.) Do you have any other idea to minimize the scheduling-related
>> latency for domain 0?
>
>
> The SEDF scheduler in the 3.0 tree should allow you to specify RT
> guarantees. Alternatively, if you have a multi-CPU system, or even
> hyperthreading, you can dedicate a cpu (or hyperthread) solely to
> domain0.
>
> -- keir
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...)
-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
Could you please try the second one and see how that works? If it works
well, I might change the default behaviour, so that the latency aware
scheduler gets enabled for a domain if it uses the latency parameter!
Cheers,
Stephan
next prev parent reply other threads:[~2005-08-08 17:16 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 [this message]
2005-08-08 21:11 ` Holger Steinhaus
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=42F79359.8050900@cam.ac.uk \
--to=sd386@cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=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.