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

xen-devel

[Top] [All Lists]

Re: [Xen-devel] [Q] about Credit Scheduler Dom0 Scheduling policy.

To: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Q] about Credit Scheduler Dom0 Scheduling policy.
From: Emmanuel Ackaouy <ack@xxxxxxxxxxxxx>
Date: 2006年10月24日 10:49:52 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2006年10月24日 02:50:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200610240647.k9O6lYQR004608@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <200610181150.k9IBoP8W031962@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20061018131115.GA5327@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20061018132410.GA5372@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200610230414.k9N4EKGJ011580@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20061023143210.GA26848@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200610240647.k9O6lYQR004608@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Oct 24, 2006 at 03:46:59PM +0900, Atsushi SAKAI wrote:
> Currently, I am testing on IA64.
> CPU=1595MHz
> itc=1595MHz
In the chunk of the trace file you sent, the scheduler is
behaving quite well. The domU being woken up at various
times on a clock boundary (10ms) must be due to some
timers.
There is one case where dom0 wakes up and doesn't preempt
the CPU (the first dom0 wake in the trace file) though. I
would like to see a bigger chunk of your trace file and
scan it to see if there are other examples of this.
If it's too big for the list, can you send it to me
privately or put it up on some publicly accessible server
somewhere?
Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] shadow2 corrupting PV guest state , Keir Fraser
Next by Date: Re: [Xen-devel] [PATCH]HVM E820 Table cleanup , Gerd Hoffmann
Previous by Thread: Re: [Xen-devel] [Q] about Credit Scheduler Dom0 Scheduling policy. , Atsushi SAKAI
Next by Thread: Re: [Xen-devel] [Q] about Credit Scheduler Dom0 Scheduling policy. , Emmanuel Ackaouy
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /