Hi, Daniel and Rich Thanks for various comments.
Qemu and Qemu with KVM uses default Linux scheduler. (struct sched_param) And Xen uses original scheduler. At this moment, we should support xen (sedf, credit) and Linux scheduler(sched_param). Is this enough? Or We should consider other parameters from Linux scheduler API? (Realtime etc...) Anyway this should be Linux scheduler related issue. So we should define Linux scheduler related struct for qemu related issue. Thanks Atsushi SAKAI Daniel Veillard <[EMAIL PROTECTED]> wrote: > On Thu, Mar 29, 2007 at 09:16:05PM +0900, Atsushi SAKAI wrote: > > Hi, Rich > > > > Thank you for your comments. > > (The primary motivation is take a comments!) > > > > I am wondering the libvirt policy about scheduer. > > And I just know the Xen scheduler only. > > Is any good idea to support this? > > So far I'm really wondering. Basically you have virtualization > specific scheduling only if the virtualization mechanism has its own > scheduler and that's only the case for Xen at the moment unless > I'm mistaken. All others reuse the scheduler of the primary Os > directly, and unless you start playing with that scheduler there is > nothing really to tune, but those changes affects far more than just > purely the virtualization side. > How would you map the API you propose with say the linux normal > scheduler APIs ? I'm a bit worried if the proposed operations are > really only making sense in a setup with the Xen hypervisor. > > Daniel > > -- > Red Hat Virtualization group http://redhat.com/virtualization/ > Daniel Veillard | virtualization library http://libvirt.org/ > [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
