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] Re: credit scheduler

To: Karl Rister <kmr@xxxxxxxxxx>
Subject: [Xen-devel] Re: credit scheduler
From: Sean Dague <japh@xxxxxxxxxx>
Date: Tue, 29 Aug 2006 17:26:02 -0400
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 29 Aug 2006 14:26:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200608281728.09181.kmr@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Karl Rister <kmr@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
References: <200608281728.09181.kmr@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Aug 28, 2006 at 05:28:08PM -0500, Karl Rister wrote:
> While doing some performance analysis of Xen I have noticed some interesting 
> behavior of the credit scheduler that I would like to see discussed.
> In my most basic test I have a 4 socket dual core Intel box (Paxville) with a 
> uniprocessor dom0 and 7 uniprocessor domUs.  Each of the domUs is pinned on 
> its own core with the first core of the system left for dom0.  When running 
> the credit scheduler the dom0 VCPU will bounce around the system, sometimes 
> landing on the same thread as one of the domUs or sometimes on one of the 
> sibling hyperthreads (this appears to happen a majority of the time it 
> moves).  This is less than ideal when considering cache warmth and the 
> sharing of CPU resources when the first core of the system is always 
> available in this configuration.  Does the credit scheduler have any 
> awareness of cache warmth or CPU siblings when balancing?

A related issue I noticed the other day when doing xen testing off of
xen-unstable was that the irqbalancer process ended up consuming 100% of
dom0 cpu when running an SMP Dom0 on the credit scheduler, and a bunch of
idle domUs.  It got the the point that ssh wasn't feasable, and I had to go
to the console and shut off irqbalancer to return things to normal.

I'd follow up further, but I'm about to go "off grid" for the next 2.5
weeks.  I relayed information to other folks on the IBM team to see if
anyone else can reproduce it.


Sean Dague
IBM Linux Technology Center                     email: japh@xxxxxxxxxx
Open Hypervisor Team                           alt: sldague@xxxxxxxxxx

Attachment: pgp5tsS27Ntml.pgp
Description: PGP signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>