[<prev] [next>] [day] [month] [year] [list]
Message-ID: <615092B2FD0E7648B6E4B43E029BCFB84D612DC1@SZXEMA503-MBS.china.huawei.com>
Date: Fri, 25 Apr 2014 02:16:28 +0000
From: "Huangpeng (Peter)" <peter.huangpeng@...wei.com>
To: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
"libvir-list@...hat.com" <libvir-list@...hat.com>
Subject: [RFC]How to improve KVM VM resource assignment and per-vm
process/thread scheduling.
Hi, ALL
Currently kvm hypervisor have lots of features depend on linux standard apis,
like vcpupin/mempin/processpin etc. But in the real production environment,
we need an automated resource assign and/or scheduling, is there any plan to
implement it?
resource assignment requirements like:
cpu eligible by the VMs
In case it is eligible, whether it is in use
if it is in use, whether it is dedicated to one VM, or can be shared by many VMs
In case of Shared CPU
need to configure oversubscription ratio
used ratio info
So does memory, I/O device assignment requirements.
per-vm process/thread scheduling requirements like:
On hypervisor side, VMs use vhost-net, virtio-scsi devices have qemu io-thread, vhost-net
thread, ovs thread, hNIC interrupt context(hirq/softirq), you shoud place there threads on the same
numa node to gain best performance, another important thing, you should balance these
threads' cpuload on all the numa cores to avoid unbalance between vcpu usable resources.
Thanks.
Peter Huang
Powered by blists - more mailing lists