[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Question on Xen schedulers


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Schmidt Werner" <Werner.Schmidt@xxxxxxxxxxxxxxxxx>
  • Date: Mon, 13 Nov 2006 14:17:12 +0100
  • Delivery-date: Mon, 13 Nov 2006 07:07:53 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AccHJgegSlXBLXrgTWOPEQOTXckmzQ==
  • Thread-topic: Question on Xen schedulers

All,
 
following the announcements and recommendations since mid of this year '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-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.