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 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Scheduling questions

To: Tim Freeman <tfreeman@xxxxxxxxxxx>
Subject: Re: [Xen-users] Scheduling questions
From: Michael Heyse <mhk@xxxxxxxxxxxxxxxxx>
Date: Tue, 10 Jan 2006 22:17:09 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Jan 2006 21:23:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060110143518.10dac0b1.tfreeman@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <43C3F378.5090909@xxxxxxxxxxxxxxxxx> <20060110123112.6ec68375.tfreeman@xxxxxxxxxxx> <20060110143518.10dac0b1.tfreeman@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
Tim Freeman wrote:
> On Tue, 10 Jan 2006 12:31:12 -0600
> Tim Freeman <tfreeman@xxxxxxxxxxx> wrote:
> 
> 
>>On Tue, 10 Jan 2006 18:48:40 +0100
>>Michael Heyse <mhk@xxxxxxxxxxxxxxxxx> wrote:
>>
>>
>>>Hi,
>>>
>>>where can I find some information about how xen-3's schedulers work and
>>>their parameters? The default setup completely locks up all domU domains
>>>on my machine (VIA Nehemiah EPIA board) whenever the dom0 domain is
>>>doing CPU/IO-intensive stuff, and the only solution I found so far is to
>>>adjust the weight of each domain (eg xm sched-sedf <domID> 0 0 0 0 1 for
>>>each domain) but this seems to be a waste of CPU capacity.
>>
>>The second to last parameter is an extra_time flag that allows a domain to use
>>extra CPU time if it is available.  Change that to '1' to allow domains to use
>>any idle CPU during the scheduling period (you must do so from dom0 as well). 

Allright, thanks for the tipp, now it's working perfectly!

> Sorry, a typo, I meant "for dom0" not "from dom0" (although the change indeed
> must be done from dom0). 

Thanks,
Michael

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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