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

To: Karl Rister <kmr@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] credit scheduler
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 29 Aug 2006 07:16:18 +0100
Delivery-date: Mon, 28 Aug 2006 23:25:42 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbLMqOW4kGwjDclEduf9QANk04WTA==
Thread-topic: [Xen-devel] credit scheduler
User-agent: Microsoft-Entourage/

On 28/8/06 11:28 pm, "Karl Rister" <kmr@xxxxxxxxxx> wrote:

> 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?

It doesn't right now, but in your setup dom0 has its 'home core' all to
itself, so it's odd that it's bouncing around. Other cores should only steal
the domain if it is runnable but not running -- that should almost never be
the case if the domain is not contending for CPU.

 -- Keir

Xen-devel mailing list

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