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/
Home Products Support Community News


Re: [Xen-devel] realtime scheduling

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] realtime scheduling
From: Stephan Diestelhorst <sd386@xxxxxxxxx>
Date: Mon, 08 Aug 2005 18:16:09 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Holger Steinhaus <hsteinhaus@xxxxxx>
Delivery-date: Mon, 08 Aug 2005 17:14:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b76ab46006c2f7dff2d29900f1c60c70@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <42F77510.5070501@xxxxxx> <b76ab46006c2f7dff2d29900f1c60c70@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
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
     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!


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>