All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [Patch 0/6] Cpupools
Date: Tue, 20 Apr 2010 11:37:58 +0200	[thread overview]
Message-ID: <4BCD75F6.3030103@ts.fujitsu.com> (raw)

Hi,

Following patch-series support cpupools in xen:

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
CPU.

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

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

             reply	other threads:[~2010-04-20  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20  9:37 Juergen Gross [this message]
2010-04-20 18:48 ` [Patch 0/6] Cpupools Ian Jackson
2010-04-21  4:44   ` Juergen Gross
2010-04-20 18:49 ` Konrad Rzeszutek Wilk
2010-04-21  4:56   ` Juergen Gross
  -- strict thread matches above, loose matches on Subject: below --
2010-04-21 11:15 Juergen Gross
2010-04-21 11:22 ` Ian Pratt
2010-04-21 11:35   ` Juergen Gross
2010-04-21 11:53 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BCD75F6.3030103@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.