WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] XCP: dom0 scalability

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] XCP: dom0 scalability
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 13 Oct 2010 09:12:18 -0700
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dave Scott <Dave.Scott@xxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 13 Oct 2010 09:13:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101013160738.GI4007@xxxxxxxxxxxxxxxxxxxxxxx>
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: <81A73678E76EA642801C8F2E4823AD219331853A47@xxxxxxxxxxxxxxxxxxxxxxxxx> <a6817c98-98bf-449b-9c05-424cee90e7cd@default> <20101013160738.GI4007@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4
 On 10/13/2010 09:07 AM, Tim Deegan wrote:
> At 16:46 +0100 on 13 Oct (1286988381), Dan Magenheimer wrote:
>> Hmmm... if dom0 is getting scheduled enough and the VMs are still
>> blocking on xenstore (i.e. the Linux scheduler in dom0 is the problem),
>> getting xenstore off of dom0 makes sense.  But if the reason xenstore
>> is not getting back to them is because dom0 is simply not getting
>> enough cpu time (i.e. the Xen scheduler is the problem), moving xenstore
>> out of there may not only NOT help, but may make things worse.  True?
> The reason that dom0's not getting enough time in this case is that it's
> running with only 1 vcpu and trying to do more than 1 vcpu worth of
> work.  I'd expect things to get very slightly better if some of that
> work can happen on another vpcu (in another dom).

Or just make dom0 multi-vcpu?

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>