public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* about CPU QoS in KVM
@ 2017-04-20 13:32 Gonglei (Arei)
       [not found] ` <33183CC9F5247A488A2544077AF19020DA237684-CArPBO0LKVoFkbVBhwfq5wK1hpo4iccwjNknBlVQO8k@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Gonglei (Arei) @ 2017-04-20 13:32 UTC (permalink / raw)
  To: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
  Cc: Jason Wang, Linqiangmin, Huangweidong (C)

Hi all,

Currently, KVM do the CPU resource reservation by the cgroup mechanism
which can't do entire accurate separation because the capacity of the Linux
scheduler. Take the public cloud as an example, some customers rent one vm
with 8 CPUs paid by enough money, they want to get enough response
speed on CPU scheduling. So we (the cloud platform providers ) reserve 1GHz
CPU resources by cgroup for those VM's vcpu/pcpu. 

But the actual effects can't meet those requirements because the cgroup is
limiting share usage of other processes in order to attach the reservation proportion,
but the scheduler can't assure that. This mechanism is different with Xen,
We can directly change the CPU weight on Xen hypervisor so that we can
get entire accurate control on CPU resources based on accurate capacity (upper limit),
share (weight) and reservation.

So my question is do we have a good method to do CPU reservation in KVM?

Thanks,
-Gonglei

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-04-26  7:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-20 13:32 about CPU QoS in KVM Gonglei (Arei)
     [not found] ` <33183CC9F5247A488A2544077AF19020DA237684-CArPBO0LKVoFkbVBhwfq5wK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2017-04-20 14:00   ` Paolo Bonzini
2017-04-25 10:13     ` Juri Lelli
2017-04-26  7:48       ` Luca Abeni

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox