mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nitesh Narayan Lal <nitesh@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Chris Friesen <chris.friesen@windriver.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [IRQ] IRQ affinity not working properly?
Date: Wed, 21 Apr 2021 09:31:37 -0400	[thread overview]
Message-ID: <fdebec53-097a-d28f-96ec-cfe8d7ef8412@redhat.com> (raw)
In-Reply-To: <87blb3ce29.ffs@nanos.tec.linutronix.de>


On 3/28/21 2:45 PM, Thomas Gleixner wrote:
> On Fri, Jan 29 2021 at 13:17, Chris Friesen wrote:
>> I have a CentOS 7 linux system with 48 logical CPUs and a number of

<snip>

>> IR-PCI-MSI-edge      iavf-net1-TxRx-3
>> 961:          0          0          0          0 28492         0 
>> IR-PCI-MSI-edge iavf-0000:b5:02.7:mbx
>> 962:          0          0          0          0 435608         0 
>> IR-PCI-MSI-edge      iavf-net1-TxRx-0
>> 963:          0          0          0          0 394832         0 
>> IR-PCI-MSI-edge      iavf-net1-TxRx-1
>> 964:          0          0          0          0 398414         0 
>> IR-PCI-MSI-edge      iavf-net1-TxRx-2
>> 965:          0          0          0          0 192847         0 
>> IR-PCI-MSI-edge      iavf-net1-TxRx-3
>>
>> There were IRQs coming in on the "iavf-0000:b5:02.7:mbx" interrupt at 
>> roughly 1 per second without any traffic, while the interrupt rate on 
>> the "iavf-net1-TxRx-<X>" seemed to be related to traffic.
>>
>> Is this expected?  It seems like the IRQ subsystem is not respecting the 
>> configured SMP affinity for the interrupt in question.  I've also seen 
>> the same behaviour with igb interrupts.
> No it's not expected. Do you see the same behaviour with a recent
> mainline kernel, i.e. 5.10 or 5.11?
>
>

Jesse pointed me to this thread and apologies that it took a while for me
to respond here.

I agree it will be interesting to see with which kernel version Chris is
reproducing the issue.

Initially, I thought that this issue is the same as the one that we have
been discussing in another thread [1].

However, in that case, the smp affinity mask itself is incorrect and doesn't
follow the default smp affinity mask (with irqbalance disabled).


[1] https://lore.kernel.org/lkml/1a044a14-0884-eedb-5d30-28b4bec24b23@redhat.com/

-- 
Thanks
Nitesh


  reply	other threads:[~2021-04-21 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 19:17 Chris Friesen
2021-03-28 18:45 ` Thomas Gleixner
2021-04-21 13:31   ` Nitesh Narayan Lal [this message]
2021-04-22 15:42     ` Thomas Gleixner
2021-04-22 17:00       ` Chris Friesen

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=fdebec53-097a-d28f-96ec-cfe8d7ef8412@redhat.com \
    --to=nitesh@redhat.com \
    --cc=chris.friesen@windriver.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome