[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] [PATCH 06/10] vcpubandwidth: introduce two new libvirt APIs
- From: "Nikunj A. Dadhania" <nikunj linux vnet ibm com>
- To: Wen Congyang <wency cn fujitsu com>, libvirt <libvir-list redhat com>, Adam Litke <agl us ibm com>
- Cc: Bharata B Rao <bharata linux vnet ibm com>
- Subject: Re: [libvirt] [PATCH 06/10] vcpubandwidth: introduce two new libvirt APIs
- Date: Mon, 04 Jul 2011 16:49:38 +0530
On Thu, 30 Jun 2011 11:13:18 +0800, Wen Congyang <wency cn fujitsu com> wrote:
> We want to control bandwidth for each vcpu, so we can not use the
> API virDomainSetSchedulerParameters(). Introduce two new APIs to
> change and query bandwidth for each vcpu.
>
Will we have different cpu bandwidth for different vcpus?
Something like this:
vcpu1: 1000000/250000
vcpu2: 1000000/500000
vcpu3: 1000000/300000
vcpu4: 1000000/400000
IMO, that is not required, we can have a top level bandwitdh for the VM
and then redistribute it among vcpus equally, without user knowing about
it.
Something like this:
VM1(4vcpu) has to be throttled at 1CPU bandwidth using SetSchedParamters.
Internally libvirt splits it equally:
vcpu1: 1000000/250000
vcpu2: 1000000/250000
vcpu3: 1000000/250000
vcpu4: 1000000/250000
So why introduce VCPU level apis?
Regards,
Nikunj
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]