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>
Subject: Re: [Xen-devel] credit scheduler
From: Emmanuel Ackaouy <ack@xxxxxxxxxxxxx>
Date: Tue, 29 Aug 2006 23:17:22 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 29 Aug 2006 15:17:46 -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.4.1i
On Mon, Aug 28, 2006 at 05:28:08PM -0500, Karl Rister wrote:
> In my testing I am looking for uniform behavior so I have just been setting 
> sched=sedf but I would like to move to credit scheduler since it is the new 
> default. However, until I sort out this behavior I cannot.

One thing you could do is restrict dom0's VCPU so that
it doesn't move around to a hyperthread on a core that
you have assigned to a domU.

So figure out what CPU dom0's VCPU is on and restrict
its cpumask so that it stays on that core. Then move
any domU out of that core.

Xen-devel mailing list

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