[Xen-users] Define caps and weights per-VCPU in credit scheduler

To:	xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-users] Define caps and weights per-VCPU in credit scheduler!
From:	"Vahid Kazempour" <kazempour@xxxxxxxxx>
Date:	Tue, 14 Oct 2008 17:48:02 -0700
Cc:
Delivery-date:	Tue, 14 Oct 2008 17:48:42 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=WaY8W8VlSzYzs6n5qFo9cgxYkO9OhkttY3cTjCP5YH8=; b=pa8wlBPkD7gRgv8knlnhuqs54UKpsoZGyDIldHYf43GnTB5FuefQkTyzGbhOmYfnBf KEjKhzVGdnojLaUN5W4J6RgnvNRtHj3F+reRh4+/JtXHwQr2kiStYSu1dLm+6BTiJSgX IgeQ5bjX+nuWSd5yVw+vo4B+BJrD3YABZVgig=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Xt5BU2EdGgDmERj3aGB098ukGvkoFt0jXszKEiT0p9Qf+ZGMTS7TWsIcCqlhkNnXJV RXfMAhRRU6167v7JPqEUol+KZPQepKCHPULUXtVYGLPdCxkbDToiTB6OlmMKHez4YDwz QUTDfpLTowDZc7xQtg+MZYkYDsaD3sI41FM7A=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi all,

As far as I know in credit scheduler we can only define weights and caps for each VM, and the scheduler apply these credits to all VCPUs belongs to the VM (i.e. if we setting a limit in the form of cap it will affect all VCPUs in the VM).

Considering a scenario that we have heterogeneous cores in the system (fast and slow cores) and VMs are competing on fast cores.
One policy for fare sharing of fast cores is to share them based on the number of VCPUs. This may require to define different limits on CPU usage for each VCPU which is not necessarily same for all VCPUs belong to a VM. In this scenario does it make sense to have weights and caps in credit scheduler based on VCPUs instead of VMs? Is it possible to define different per-VCPU limits for a single VM without modifying the scheduler code?

Thanks,

--
Vahid Kazempour

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

WARNING - OLD ARCHIVES

xen-devel

[Xen-users] Define caps and weights per-VCPU in credit scheduler!