Re:Re: Is guest OS oriented scheduling welcome?

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

 



just now, I tried cgroup. I admit that as far as only CPU share is
concerned, cgroup is enough.

However, AFAIK Linux schedules each thread independently, ignoring the
upper level logic.

for example, suppose VM1 is an SMP one, and it is used to receive
network packets, which causes it run the TCP/IP stack code frequently.
The use of spin-lock implies that the lock holder will release it
fast. However, when vcpu threads are scheduled independently, when one
vcpu is spinning, the lock holder might be off the CPU! This would
make the VM's SMP scalability bad.

And there are user level vcpu dependence too.

Regards,
alex.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux