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

[Xen-devel] Question on xen schedulers

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Question on xen schedulers
From: "Schmidt Werner" <Werner.Schmidt@xxxxxxxxxxxxxxxxx>
Date: Wed, 15 Nov 2006 17:48:39 +0100
Delivery-date: Thu, 16 Nov 2006 00:44:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccI1easuJFdMvIDSZ+8/RchJsgChA==
Thread-topic: Question on xen schedulers
All,
 
i had sent the mail below to xen-user mailing list before, but not got any helpful reaction. Probably it is really more a question for the xen-devel list; i would appreciate any useful  info on this topic:  
 
'credit' is now the (only) recommended scheduler and the others ('bvt', 'sedf') are already removed from the latest Xen 3.0 sources or will be removed in the future.
Now, 'credit' is designed for an optimum utilisation of a SMP system and may be really the best scheduler for this purpose. But i think this is not the only useful scenario for the usage of Xen; there maybe other scenarios with other demands, e.g. 'soft' real-time systems and/or single processor systems.
If i remember correctly, one of the major advantages mentioned in the first announcements of Xen 3.0 was the support of multiple schedulers (for different purposes). Could give anyone the reasons why this approach is not longer valid and what is the reason to kick out the already existing more 'real-time friendly' schedulers, especially sedf ?
 
Thanks
 
Werner
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>