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


greedy dom0 in sedf fixed! (Re: [Xen-devel] More on sedf scheduler)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: greedy dom0 in sedf fixed! (Re: [Xen-devel] More on sedf scheduler)
From: Stephan Diestelhorst <sd386@xxxxxxxxxxxx>
Date: Fri, 22 Jul 2005 18:20:15 +0100
Cc: Rob Gardner <rob.gardner@xxxxxx>
Delivery-date: Fri, 22 Jul 2005 17:18:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42D6ABE6.1030502@xxxxxx>
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>
References: <1121191749.3860.4.camel@xxxxxxxxxxxxxxxxxxxxxxx> <200507141839.58983.sd386@xxxxxxxxxxxx> <42D6ABE6.1030502@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
Am Donnerstag, 14. Juli 2005 19:16 schrieb Rob Gardner:
> Stephan Diestelhorst wrote:
> >Thanks,
> >  what is your dom0 tight loop doing? Heavy I/O?
> >It looks like dom0 does a lot of I/O, which immediatelly unblocks and then
> >gets a higher priority in the L1 extraq, without anybounds on
> > executiontime, i.e. slice length. Can you confirm this?
> >
> >Stephan
> The loop was just while(1); There was also a python script running that
> was reading from xentrace. So no heavy i/o, at least no disk/network
> i/o. But that doesn't matter anyway. Here is another dump where dom0 is
> doing absolutely nothing besides while (1); And dom1 is completely
> comatose during this time.
> Rob
Should be fixed in the current repository!


Xen-devel mailing list