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

Fwd: [Xen-devel] Question Also regarding interrupt balancing

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Fwd: [Xen-devel] Question Also regarding interrupt balancing
From: harish <mvharish@xxxxxxxxx>
Date: Thu, 29 Jun 2006 12:13:41 -0700
Delivery-date: Thu, 29 Jun 2006 12:14:10 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=irBXFAtVITZRNMu4EZ7BCC+O0yuOioEgrNairqccEyDFoVO90bcHIBFRleduQN30Sr9D6XOf951az5E4hCfHFO4pmXaxgJcia+of0IhXmCEHhqSYTVViPHkmjvN/fUwIJwr+48TpMOOSixtncJTHejRWBAK0ejmoMg85pEP9hN4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <a33d0a9f0606291140i1b53f6acjb34cc94362d4ae77@xxxxxxxxxxxxxx>
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: <a33d0a9f0605220943q75af2d77m8fbf1508a2ad9a88@xxxxxxxxxxxxxx> <a33d0a9f0606091139w5e5178f7x28d98db5721ceb76@xxxxxxxxxxxxxx> <260b1f3e22421d58dd152a6969f106fc@xxxxxxxxxxxx> <a33d0a9f0606100958i75dd812at1fa420966f92189b@xxxxxxxxxxxxxx> <9bae6f237b7ec1b9cd78ca745bee1e41@xxxxxxxxxxxx> <a33d0a9f0606121642k40b0b3cao5bc0473944ad2ee7@xxxxxxxxxxxxxx> <0dc18039de2a59cc81de532ca1ba5f3e@xxxxxxxxxxxx> <a33d0a9f0606290851r76d9438cr55565def4b987645@xxxxxxxxxxxxxx> <c1cd43a488a9548127a249f2efac95c5@xxxxxxxxxxxx> <a33d0a9f0606291140i1b53f6acjb34cc94362d4ae77@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
FWD...forgot to cc the group.

-
I was not clear in my last email and so trying to rephrase the question with an example:

peth0   --> pcpu2 [mapped this using the proc interface]
domU1 --> pcpu3

Noticed that the physical interrupts were getting routed to pcpu2 and so the mapping worked. However noticed that there were significant number of virtual interrupts corresponding to vif1.0 [used by domU1]. The interrupts were serviced by pcpu0. It is this interrupts that I was talking about in my earlier question.

I thought interrupts of type "Dynamic-irq" in general cannot be set using proc interface. Please correct me if I am wrong but from your response below it looks like we can. Anyways I tried setting it using the /proc interface for the virtual interrupts corresponding to vif1.0 and it did not work.

How are the virtual interrupts mapped? Yet to see a test where the virtual interrupts run on a pcpu other than pcpu0 and so wondering if there is a explicit mapping in the code.

Hope my question makes sense now?

-hmv



On 6/29/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

On 29 Jun 2006, at 16:51, harish wrote:

>  And ran a quick netperf test. Noticed that the cpu utilization was
> around ~50% on pcpu0 although my interrupts were being pinned to pcpu2
> and domU on pcpu3. That is when I noticed that vif#id.0 has a dynamic
> irq which is serviced by pcpu0. Does this irq always run on pcpu0?
> Considering that it is dynamic, I understand that we cannot change the
> affinity and so am wondering if there some other configuration related
> to it.

Again, we don't load balance in the kernel, but you could change its
affinity to some other single CPU via the proc interface.

  -- Keir


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