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] realtime scheduling

Subject: Re: [Xen-devel] realtime scheduling
From: Holger Steinhaus <hsteinhaus@xxxxxx>
Date: Mon, 08 Aug 2005 23:11:03 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 08 Aug 2005 21:09:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42F79359.8050900@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/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> <42F79359.8050900@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050716)

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

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

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