From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
gabriel@krisman.be, hch@lst.de, linuxppc-dev@lists.ozlabs.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] genirq/affinity: fix node generation from cpumask
Date: Wed, 14 Dec 2016 23:05:51 -0200 [thread overview]
Message-ID: <87oa0erogg.fsf@collabora.co.uk> (raw)
In-Reply-To: <1481738472-2671-1-git-send-email-gpiccoli@linux.vnet.ibm.com> (Guilherme G. Piccoli's message of "Wed, 14 Dec 2016 16:01:12 -0200")
"Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com> writes:
> Commit 34c3d9819fda ("genirq/affinity: Provide smarter irq spreading
> infrastructure") introduced a better IRQ spreading mechanism, taking
> account of the available NUMA nodes in the machine.
>
> Problem is that the algorithm of retrieving the nodemask iterates
> "linearly" based on the number of online nodes - some architectures
> present non-linear node distribution among the nodemask, like PowerPC.
> If this is the case, the algorithm lead to a wrong node count number
> and therefore to a bad/incomplete IRQ affinity distribution.
>
> For example, this problem were found in a machine with 128 CPUs and two
> nodes, namely nodes 0 and 8 (instead of 0 and 1, if it was linearly
> distributed). This led to a wrong affinity distribution which then led to
> a bad mq allocation for nvme driver.
>
> Finally, we take the opportunity to fix a comment regarding the affinity
> distribution when we have _more_ nodes than vectors.
Thanks for taking care of this so quickly, Guilherme.
Reviewed-by: Gabriel Krisman Bertazi <gabriel@krisman.be>
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2016-12-15 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 18:01 [PATCH] genirq/affinity: fix node generation from cpumask Guilherme G. Piccoli
2016-12-14 23:24 ` Gavin Shan
2016-12-15 9:36 ` Thomas Gleixner
2016-12-15 12:38 ` Guilherme G. Piccoli
2016-12-15 1:05 ` Gabriel Krisman Bertazi [this message]
2016-12-15 8:54 ` Christoph Hellwig
2016-12-15 11:37 ` [tip:irq/urgent] genirq/affinity: Fix " tip-bot for Guilherme G. Piccoli
2016-12-15 12:34 ` [PATCH] genirq/affinity: fix " Balbir Singh
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=87oa0erogg.fsf@collabora.co.uk \
--to=gabriel@krisman.be \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.