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] ksoftirq/0 eating all cpu time

To: "Hans-Christian Armingeon" <mog.johnny@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] ksoftirq/0 eating all cpu time
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 12 Apr 2006 16:58:27 +0100
Delivery-date: Wed, 12 Apr 2006 08:58:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZeQaSSMzDYy902QbWK3cy0nXj6hAABeRBQ
Thread-topic: [Xen-devel] ksoftirq/0 eating all cpu time
> But the other Problem I have with this machine is, that when 
> I run a make -j3 in dom0, the domUs are very slow, even if 
> there is only one domU.

The default scheduling parameters are set assuming that the only thing
running in dom0 is the control tool stack and the physical device
If you're actually logged in and running stuff in dom0 then the defaults
are terrible as they basically give dom0 much higher priority than
everything else.


Xen-devel mailing list

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