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


[Xen-devel] RE: [Patch] Fix IDLE issue with sedf scheduler on IA64

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: [Xen-devel] RE: [Patch] Fix IDLE issue with sedf scheduler on IA64
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Wed, 13 Jul 2005 05:24:38 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jul 2005 12:23:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcWHkNam4njROoPTSRq2Lw7NMoU4SwAE6cuA
Thread-topic: [Patch] Fix IDLE issue with sedf scheduler on IA64
>       To make ac_timer softirq triggered more precisely, another
> parameter tuned in the patch is the HZ, changed from 100(10ms) to
> 1024(1ms). Then the cpu_time of IDLE is decreased to about 0.09% from
> previous %1.

Hmmm... Are there other side effects from the HZ=32?  This patch
costs an extra ~1000 interrupts/second.  Since each of these interrupts
need to be handled in C code, the save/restore overhead is a large
fraction of the cost of a domain switch, thus increasing the total
Xen overhead (on _every_ application, even one which is CPU bound)
substantially.  Well, maybe not _substantially_ but probably on the
order of 0.1%.

Is there a better way (for ia64)?  I kind of like the solution
Keir and Ian imply... is it possible in context_switch to simply
"refuse" to switch to the idle domain?   E.g. if the idle domain
is the target of the switch, instead switch to domain0 (and
make it runnable)?


P.S. If this can be done in ia64-specific code, let's switch this
thread to xen-ia64-devel.  If not, we can later move the discussion
back to xen-devel.

Xen-devel mailing list