From: Ming Lei <ming.lei@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [PATCH 0/2] genriq/affinity: two improvement on __irq_build_affinity_masks
Date: Fri, 9 Aug 2019 18:23:08 +0800 [thread overview]
Message-ID: <20190809102310.27246-1-ming.lei@redhat.com> (raw)
Hi,
The 1st patch makes __irq_build_affinity_masks() more reliable, such as,
all nodes can be covered in the spread.
The 2nd patch spread vectors on node according to the ratio of this node's
CPU number to number of all remaining CPUs, then vectors assignment can
become more fair. Meantime, the warning report from Jon Derrick can be
fixed.
Please review & comment!
Ming Lei (2):
genirq/affinity: improve __irq_build_affinity_masks()
genirq/affinity: spread vectors on node according to nr_cpu ratio
kernel/irq/affinity.c | 46 +++++++++++++++++++++++++++++++------------
1 file changed, 33 insertions(+), 13 deletions(-)
Cc: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org,
Cc: Jon Derrick <jonathan.derrick@intel.com>
--
2.20.1
next reply other threads:[~2019-08-09 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 10:23 Ming Lei [this message]
2019-08-09 10:23 ` [PATCH 1/2] genirq/affinity: improve __irq_build_affinity_masks() Ming Lei
2019-08-09 14:42 ` Keith Busch
2019-08-09 23:05 ` Ming Lei
2019-08-12 5:06 ` Ming Lei
2019-08-09 10:23 ` [PATCH 2/2] genirq/affinity: spread vectors on node according to nr_cpu ratio Ming Lei
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=20190809102310.27246-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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