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


[Xen-devel] [Patch 0/6] Cpupools

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [Patch 0/6] Cpupools
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date: Wed, 21 Apr 2010 13:15:44 +0200
Delivery-date: Wed, 21 Apr 2010 04:16:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1271848610; x=1303384610; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; z=Message-ID:=20<4BCEDE60.9070108@xxxxxxxxxxxxxx>|Date:=20 Wed,=2021=20Apr=202010=2013:15:44=20+0200|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>|MIME-Version: =201.0|To:=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel @lists.xensource.com>|Subject:=20[Patch=200/6]=20Cpupools |Content-Transfer-Encoding:=207bit; bh=wYvVzbvsKHcdmnNrrRzrCN/RBZTEvZAc4eDF5YRl2hE=; b=WD9navSJ7wkZuvQuw4RQ7uyIYAOqufZRqkkvK24x8muKge+zxDbAnGCw Hgq0Ozy9P0UjDT6UqR02CciJ2X4UHZkUYMw7C3z2QNLYcg8CWhbVql6KX 76wz0uuPj8ud5Lzc88YzqNqDEqJbL7z7MtDbFoQXbIouzfIU0FJenIuUU dMgtdowIr3IH1Nn3WRlFK9BcqZ9Mx6dn1rwK0Se5cBdTNswyz4JvStOe9 4G05Jsclimhlyb8vaGzNMETzW4Kd3;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:Subject:X-Enigmail-Version: Content-Type:Content-Transfer-Encoding; b=B0XqTkb2UB/Uzfec6E8Kr7xiFRSZsmnRCW15y/D0TIS1WrcE2cjnZIWE mGRiEt54Ez2TtQqHY3/LYF/WwUmLO5Lv76K1vDdARJ7Lx4x7LKAHylxvs wLpd7jw7rlO8mNKEdBTeeVqk2KNXQ9qj0P6CAEbRP//AYtekGOeoL6LdH TrMP8bzubGF53X8ZRxEJOr3o1nd0fK4K8EAdCMoCKg+n1eZw56WdoLPPu bu5FtP/cbTnJ+O+FNr1NsbCzKI2gZ;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Organization: Fujitsu Technology Solutions
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird (X11/20100329)
Round 2 for cpupools patches.

Changes from 1st version:
- create all domains in Pool-0, move to specific pool afterwards
- don't use cpupool_lock for cpu add/remove. Races with hot swapping cpus are
  avoided by locking cpus to Pool-0 if necessary

libxl patches will be sent soon, I'm still working on them.

The physical cpus of a server are grouped in cpu-pools. Each physical CPU is
assigned at most to one cpu-pool. Domains are each restricted to a single
cpu-pool. Scheduling does not cross cpu-pool boundaries, so each cpu-pool
has an own scheduler.

The cpu-pool of the domain Dom0 will be Pool-0, at boot-time we have to create
this cpu-pool implicitly.

The creation of a cpu-pool is similar to the creation of a domain. In a first
step the attributes of a cpu-pool have to be defined, in the second step the
cpu-pool will be activated (started) by assigning the resources (CPUs) and
initializing the scheduler. An activated cpu-pool owns at least one physical

A physical CPU may be removed from an activated cpu-pool. Further CPUs may be
assigned to the cpu-pool. The CPU may be assigned to a cpu-pool only if that
CPU is free (not assigned to any other activated cpu-pool). The free CPUs are
internally managed.

The poolname will be added as an additional parameter to the configfile of a
domain. If no poolname is specified the poolname is defaults to Pool-0. At
domain start the domain is added to its cpu-pool, which must be activated.

A started domain can be moved to another activated cpu-pool.

A cpu-pool may be deactivated if there is no active domain assigned to it. A
cpu-pool is deactivated by removing the resources (CPUs).

A cpu-pool may be deleted if it is deactivated.

The administration of the cpu-pools is done by xm subcommands.

Patch 1/6: hypervisor support of cpupools
Patch 2/6: support in libxc
Patch 3/6: changes in libxen
Patch 4/6: python stuff (xm, xend)
Patch 5/6: xm-test add-ons for cpupools
Patch 6/6: documentation changes


Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

Xen-devel mailing list