From: Paolo Bonzini <pbonzini@redhat.com>
To: KVM list <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
cgroups@vger.kernel.org
Cc: Gonglei <arei.gonglei@huawei.com>,
"Jason Wang (jasowang@redhat.com)" <jasowang@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
linqiangmin@huawei.com, Rik van Riel <riel@redhat.com>
Subject: Re: about CPU QoS in KVM
Date: Thu, 20 Apr 2017 16:00:50 +0200 [thread overview]
Message-ID: <8a5470cd-0cb2-5019-c7d3-7c407e6a6005@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA237684@DGGEMA505-MBS.china.huawei.com>
Adding Rik.
Paolo
On 20/04/2017 15:32, Gonglei (Arei) wrote:
> 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
>
>
next prev parent reply other threads:[~2017-04-20 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:32 Gonglei (Arei)
2017-04-20 14:00 ` Paolo Bonzini [this message]
2017-04-25 10:13 ` Juri Lelli
2017-04-26 7:48 ` Luca Abeni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a5470cd-0cb2-5019-c7d3-7c407e6a6005@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linqiangmin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=weidong.huang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome