From: Thomas Gleixner <tglx@linutronix.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Romain Bezut <rbezut@gmail.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH] PCI/MSI: Export all remapped MSIs to sysfs attributes
Date: Sun, 11 Oct 2015 11:49:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1510111148340.6097@nanos> (raw)
In-Reply-To: <20151009223315.GC16112@localhost>
On Fri, 9 Oct 2015, Bjorn Helgaas wrote:
> On Thu, Sep 24, 2015 at 01:31:16AM +0200, Romain Bezut wrote:
> > irqbalance uses these attributes to populate its internal database, which is
> > then used to bind the irq on the appropriate NUMA node.
> >
> > On a device accepting multiple MSIs and with interrupt remapping enabled,
> > only the first irq entry is exported to msi_irqs directory.
> > This results in irqbalance having no clue of the NUMA affinity for the extra
> > irqs and starting to bind them on random nodes.
> >
> > This patch exports all MSI interrupts as sysfs attributes when relevant.
> >
> > Signed-off-by: Romain Bezut <rbezut@gmail.com>
>
> This seems like it makes sense to me. Do you have any bug reports
> related to this problem? If so, I'll mention them in the changelog.
>
> Added Neil, Thomas, and linux-kernel since this is of interest to folks
> beyond the usual linux-pci audience.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2015-10-11 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 23:31 [PATCH] PCI/MSI: Export all remapped MSIs to sysfs attributes Romain Bezut
2015-10-09 22:33 ` Bjorn Helgaas
2015-10-11 9:49 ` Thomas Gleixner [this message]
2015-10-15 17:23 ` Bjorn Helgaas
2017-01-23 20:57 ` Myron Stowe
2017-01-23 21:49 ` Neil Horman
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=alpine.DEB.2.11.1510111148340.6097@nanos \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rbezut@gmail.com \
/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