xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: David Vrabel <david.vrabel@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] Changing netback tx interrupts affinity on Dom0
Date: Fri, 4 Sep 2015 14:28:18 +0100	[thread overview]
Message-ID: <55E99C72.3030503@citrix.com> (raw)
In-Reply-To: <CAHyh4xjjiSpx29=NOZ+CTzCr996kdmWPqQquSPNb8n-+M7bzpg@mail.gmail.com>

Hi,

On 03/09/15 22:12, Jintack Lim wrote:
> On Thu, Sep 3, 2015 at 2:21 PM, Julien Grall <julien.grall@citrix.com
> <mailto:julien.grall@citrix.com>> wrote:
> 
>     On 03/09/15 17:06, Jintack Lim wrote:
>     > Hi,
> 
>     Hi Jintack,
> 
>     > On Thu, Sep 3, 2015 at 11:34 AM, Ian Campbell <ian.campbell@citrix.com <mailto:ian.campbell@citrix.com>
>     > <mailto:ian.campbell@citrix.com <mailto:ian.campbell@citrix.com>>>
>     wrote:
>     >
>     >     On Thu, 2015-09-03 at 10:59 -0400, Jintack Lim wrote:
>     >     > Hi,
>     >     >
>     >     > While I was running Apache server,
>     >     > I found that one of Dom0 vcpu is running 100% to handle irqs,
>     >     > and those irqs are set to be processed only on that specific
>     vcpu.
>     >     >
>     >     > Referring to this document,
>     >     >
>     http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide
>     >     > I tried to change smp_affinity by writing a value to
>     /proc/irq/<irq
>     >     > -no>/smp_affinity,
>     >     > however the smp_affinity value was not changed.
>     >     >
>     >     > I'm working on Xen 4.5 on ARMv8,
>     >     > and the irq is netback tx interrupt.
>     >     >
>     >     > # cat /proc/irq/106/smp_affinity
>     >     > 1
>     >     >
>     >     > # cat /proc/interrupts
>     >     > ...
>     >     > 106:      53849          0          0          0   xen-dyn-event
>     >     > vif1.1-q0-tx
>     >     > 107:          1          0          0          0   xen-dyn-event
>     >     > vif1.1-q0-rx
>     >     > 108:      61460          0          0          0   xen-dyn-event
>     >     > vif1.1-q1-tx
>     >     > 109:          1          0          0          0   xen-dyn-event
>     >     > vif1.1-q1-rx
>     >     > 110:      67118          0          0          0   xen-dyn-event
>     >     > vif1.1-q2-tx
>     >     > 111:          1          0          0          0   xen-dyn-event
>     >     > vif1.1-q2-rx
>     >     > 112:      58273          0          0          0   xen-dyn-event
>     >     > vif1.1-q3-tx
>     >     > 113:          1          0          0          0   xen-dyn-event
>     >     > vif1.1-q3-rx
>     >     > ...
>     >     >
>     >     > What would be the way to change smp_affinity?
> 
>     All those interrupts are in-fine event channels. This is a bug in Linux
>     which I sent a fix a month ago and it's queued in xentip for Linux
>     4.3 [1]
> 
>     The event channel rebinding was not working because we don't have vector
>     callback on ARM and therefore the driver was only allowing event channel
>     to be routed on VCPU0.
> 
> 
> After applying this patch, I was able to set smp_affinity.
> 
> In addition, the default value of smp_affinity for netback tx interrupts
> on Dom0 becomes "f" (I have four vcpus on Dom0).
> What I meant by 'netback tx interrupts' is vif1.1-q<num>-tx
> This is slightly different from x86, because netback tx interrupts are
> pinned to separate vcpus on x86.
> I'm not sure this question is appropriate for devel-list,
> but why the policy to set smp_affinity for netback tx interrupts are
> different on ARM and x86?

I'm not sure why. By default on both ARM and x86 the IRQ code is setting
the affinity to all the vCPU.

Note that you are likely using PV for x86 DOM0 which is different than
HVM so it may be possible that we differ for setting the affinity.

I've CCed David who was working on the event channel code. It may have
more insights.

Regards,

-- 
Julien Grall

      reply	other threads:[~2015-09-04 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHyh4xj3+si5+TzSGJeN3Wp0VE8MnPV30BFc_b7c+uuW+o+2mw@mail.gmail.com>
     [not found] ` <1441294496.26292.372.camel@citrix.com>
2015-09-03 16:06   ` [Xen-users] Changing netback tx interrupts affinity on Dom0 Jintack Lim
2015-09-03 17:30     ` Jintack Lim
2015-09-03 18:21     ` Julien Grall
2015-09-03 21:12       ` Jintack Lim
2015-09-04 13:28         ` Julien Grall [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E99C72.3030503@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jintack@cs.columbia.edu \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).