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] [Patch][resend] implementation of cpupool support in xl

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch][resend] implementation of cpupool support in xl
From: Vasiliy G Tolstov <v.tolstov@xxxxxxxxx>
Date: Thu, 16 Sep 2010 17:02:42 +0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 16 Sep 2010 06:05:36 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=selfip.ru; s=dk; h=Content-Transfer-Encoding:Mime-Version:Message-ID:Date:Content-Type:References:In-Reply-To:Cc:To:Reply-To:From:Subject; bh=acWPrt1ImXGBML7w47zsgcPQDdjtKhftdZU8ZdVqwfg=; b=MqNx2XjqDst3L9AaPkW0kjvJTO14xd68bFQ9WZkpmPSado9YGTuYQ/Gt3woZFESfVc/PRRmEqRKy06mT7EXdyB8+81Ab1FZbl6PYlg+dHWQFxooMODVnxHc04DNG0iHW;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C921517.9070605@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>
Organization: Selfip.Ru
References: <4C907510.3070904@xxxxxxxxxxxxxx> <1284616684.4860.16.camel@xxxxxxxxx> <4C921517.9070605@xxxxxxxxxxxxxx>
Reply-to: v.tolstov@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
В Чтв, 16/09/2010 в 15:01 +0200, Juergen Gross пишет:
> 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

Thank you very much!

Vasiliy G Tolstov <v.tolstov@xxxxxxxxx>

Xen-devel mailing list