From mboxrd@z Thu Jan  1 00:00:00 1970
From: Emmanuel Ackaouy <ack@xensource.com>
Subject: Re: [Q] about Credit Scheduler Dom0 Scheduling policy.
Date: Wed, 18 Oct 2006 14:24:10 +0100
Message-ID: <20061018132410.GA5372@cockermouth.uk.xensource.com>
References: <200610181150.k9IBoP8W031962@fjmscan502.ms.jp.fujitsu.com>
	<20061018131115.GA5327@cockermouth.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20061018131115.GA5327@cockermouth.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Atsushi SAKAI <sakaia@jp.fujitsu.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Wed, Oct 18, 2006 at 02:11:15PM +0100, Emmanuel Ackaouy wrote:
> If dom0 isn't preempting, in theory that is for one of
> two reasons:
> 1- It's consumed its fair share of CPU already.
> 2- It's been inactive for a while.

I should add that if (1), then increasing the weight of dom0
should solve the problem. Try doubling it.

If (2), then I'd like to see the xentrace output for a few
seconds worth of running your workload.