This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Cpu pools discussion

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Cpu pools discussion
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Tue, 28 Jul 2009 13:50:08 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Zhigang Wang <zhigang.x.wang@xxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 28 Jul 2009 05:50:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=CBMRKQ1zdPVzMu7iyvtP+bJNMnWkJV0QCxxtTpFebFo=; b=CFUOIullqt7S63E3abnAn/GFOczrm/b2pL975lRv41vg/ZjfZxLxvcg9ifxOxIv5tm 6jndo3HJuTeHdXb2eGSQvL2a9ZXIITuq2eZuIViTtqbPyty4WisHwtc/vAO+0cIyluy2 s9OPfU2EpUqisTxMFnw2xP/E2xIETQjVHOKhs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=lLydX53jHddWr8qdrBoqXBr7St7ogcx6l8Oyg3EFqbDk0kJdiH5bGAigLlm2Hs0Dvm pMk6CeETAvTpi36zWoPrvc59fFdKyPSx4iibILw8lvYlF64C8XBuwzb8Es9L/C1vt4i3 z91HeFbe3lWqTDXlrawT9kfrdeKEm4DBZnGug=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A6ECFD3.4030709@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <de76405a0907270820gd76458cs34354a61cc410acb@xxxxxxxxxxxxxx> <4A6E492D.201@xxxxxxxxxx> <20090728091929.GI5235@xxxxxxxxxxxxxxxxxxxxx> <4A6ECFD3.4030709@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Jul 28, 2009 at 11:15 AM, Juergen
Gross<juergen.gross@xxxxxxxxxxxxxx> wrote:
> Tim Deegan wrote:
>> That's easily done by setting affinity masks in the tools, without
>> needing any mechanism in Xen.
> More or less.
> You have to set the affinity masks for ALL domains to avoid scheduling on the
> "special" cpus.
> You won't have reliable scheduling weights any more.

I think this is the key thing: scheduling algorithms normally ignore
pinning.  Both credit1 and (atm) credit2 assume that a VM with higher
credit will be able to run before a VM of lower credit.  But if there
are some VMs pinned to a subset of pcpus, and other VMs pinned on
another subset (or not pinned at all), this breaks that assumption.
The algorithms might be able to be extended to account for pinning,
but it would make things a lot more complicated.  This means harder to
understand and modify the algorithm, which means it's likely to break
in the future as people try to extend it.  It also means any future
updates or rewrites have to take this pin-to-partition case into
account and do the "right thing".

Given that people want to partition a machine, I think cpu pools makes
the most sense:
* From a user perspective it's easier; no need to pin every VM, simply
assign which pool it starts in
* From a scheduler perspective, it makes thinking about the algorithms
easier.  It's OK to build in the assumption that each VM can run
anywhere.  Other than partitioning, there's no real need to adjust the
scheduling algorithm to do it.


> Juergen
> --
> Juergen Gross                 Principal Developer Operating Systems
> TSP ES&S SWE OS6                       Telephone: +49 (0) 89 636 47950
> Fujitsu Technolgy Solutions               e-mail: juergen.gross@xxxxxxxxxxxxxx
> Otto-Hahn-Ring 6                        Internet: ts.fujitsu.com
> D-81739 Muenchen                 Company details: ts.fujitsu.com/imprint.html
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list