All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: v.tolstov@selfip.ru
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch][resend] implementation of cpupool support in xl
Date: Thu, 16 Sep 2010 15:01:11 +0200	[thread overview]
Message-ID: <4C921517.9070605@ts.fujitsu.com> (raw)
In-Reply-To: <1284616684.4860.16.camel@vase.work>

On 09/16/10 07:58, Vasiliy G Tolstov wrote:
> Sorry for may be breaking thread, but what benefits of using cpu pool in
> Xen? Can You provide some use cases for using cpu pools?

Without cpu pools the whole Xen server is running one scheduler which is
scheduling all domains on all cpus (possibly with some restrictions due to
cpu pinning). With cpu pools each pool is running it's own scheduler
responsible only for some cpus and some domains. This may be important if
you want to:
- isolate some domains from others regarding cpu usage
- restrict a group of domains to a subset of cpus (e.g. due to license
   restrictions), while scheduling parameters should still be working (this was
   our main problem without cpu pools: scheduling weights and cpu pinning are
   not working together very well)
- use different scheduling strategies for different domains (e.g. credit
   scheduler for some domains and credit2 or sedf for others)

For an extended discussion on cpu pools please see:
http://lists.xensource.com/archives/html/xen-devel/2009-07/msg01116.html


HTH 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-09-16 13:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15  7:26 [Patch][resend] implementation of cpupool support in xl Juergen Gross
2010-09-15  8:29 ` Ian Campbell
2010-09-15  8:45   ` Juergen Gross
2010-09-15  9:16     ` Ian Campbell
2010-09-15  9:23       ` Juergen Gross
2010-09-15  9:37         ` Ian Campbell
2010-09-15 10:22           ` Ian Campbell
2010-09-15 11:28             ` Juergen Gross
2010-09-15 15:35               ` Ian Campbell
2010-09-16  5:48                 ` Juergen Gross
2010-09-16 17:24                   ` Ian Jackson
2010-09-16  5:58 ` Vasiliy G Tolstov
2010-09-16 13:01   ` Juergen Gross [this message]
2010-09-16 13:02     ` Vasiliy G Tolstov
2010-09-16 10:45 ` Ian Campbell
2010-09-16 12:02   ` Juergen Gross
2010-09-16 17:22     ` Ian Jackson

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=4C921517.9070605@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=v.tolstov@selfip.ru \
    --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.