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-devel

Re: [Xen-devel] Interrupt Affinity Question

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Interrupt Affinity Question
From: "Pradeep Vincent" <pradeep.vincent@xxxxxxxxx>
Date: Sat, 14 Apr 2007 01:06:23 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 14 Apr 2007 01:05:36 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=f4Ed7a8kPUKmLz0of6mdfdkK+PcN8fWfRvA8pm+MD+wILR8SMH5pzKQmU2zWlKgSVVc8JaKTq2wCntf7irYpg6ZdTqGvlofIcHgsNWG6lwpejLRxkL17kDJNCHMANnWAauQbyLa2/2fbRAP9RQbDwW2GdY2rT/PifRFmEk2MoYY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZudO4u+O2RSDkHfweqQYDnDMHb2GlSMg3k64V8Kk+BZUk269+BiOtqYno+JoLov884nwmwPmBY1BKDmCPeeg9jRIrP5hyWjcNwnNcCSy1MBbYDAFQ0sAczCadwFiV73i4Fw/KVPOSytslKIyvc6c2IoaeeUmxIbFbspNyiZ4woU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C24637B1.5D98%Keir.Fraser@xxxxxxxxxxxx>
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: <9fda5f510704132033o7e769048kfe01b006ed777ae3@xxxxxxxxxxxxxx> <C24637B1.5D98%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Wouldn't it be better to set dom0_vcpus_pin by default when dom0 is
handling all the I/O. dom0 clearly should have high priority (weight)
to avoid excessive I/O latency and hence none of the dom-0 vcpu would
be left waiting in the runq for too long.

Only problem would be relatively rare schedule-latency hit due to lack
of ability to migrate but I am wondering if this would be better
trade-off.

Thanks Keir,

- Pradeep Vincent


On 4/13/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
On 14/4/07 04:33, "Pradeep Vincent" <pradeep.vincent@xxxxxxxxx> wrote:

> If dom-0 vcpu to pcpu affinity is not set (dom0_vcpus_pin not set),
> what happens when dom-0 vcpu migrates - is the  processor affinity of
> the irq channels changed by some means to reflect the migration  or do
> the hardware interrupts end up going to the old processor while the
> pirq will be served by the dom-0 vcpu on a different processor ?

This doesn't happen right now. What we may need to do is measure the cost of
needing to forward the interrupt to the correct CPU, in the case that the
VCPU is currently running on a different CPU, versus the cost of
reprogramming an IOAPIC register. Also important is to know how rapidly the
credit scheduler is moving VCPUs among CPUs, and hence the average number of
interrupts between movements.

 -- Keir




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

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