From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH V3 0/3] genriq/affinity: Make vectors allocation fair
Date: Tue, 13 Aug 2019 16:14:44 +0800 [thread overview]
Message-ID: <20190813081447.1396-1-ming.lei@redhat.com> (raw)
Hi,
The 1st patch enhances one warning check.
The 2nd patch makes __irq_build_affinity_masks() more reliable, such as,
all nodes can be covered in the spread.
The 3rd 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!
V3:
- re-order the patchset
- add helper of irq_spread_vectors_on_node()
- handle vector spread correctly in case that numvecs is > ncpus
- return -ENOMEM to API's caller
V2:
- add patch3
- start to allocate vectors from node with minimized CPU number,
then every node is guaranteed to be allocated at least one vector.
- avoid cross node spread
Ming Lei (3):
genirq/affinity: Enhance warning check
genirq/affinity: Improve __irq_build_affinity_masks()
genirq/affinity: Spread vectors on node according to nr_cpu ratio
kernel/irq/affinity.c | 191 ++++++++++++++++++++++++++++++++++--------
1 file changed, 158 insertions(+), 33 deletions(-)
Cc: Jens Axboe <axboe at kernel.dk>
Cc: Christoph Hellwig <hch at lst.de>
Cc: Keith Busch <kbusch at kernel.org>
Cc: linux-nvme at lists.infradead.org,
Cc: Jon Derrick <jonathan.derrick at intel.com>
--
2.20.1
next reply other threads:[~2019-08-13 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 8:14 Ming Lei [this message]
2019-08-13 8:14 ` [PATCH V3 1/3] genirq/affinity: Enhance warning check Ming Lei
2019-08-13 19:31 ` Derrick, Jonathan
2019-08-14 8:58 ` Ming Lei
2019-08-13 8:14 ` [PATCH V3 2/3] genirq/affinity: Improve __irq_build_affinity_masks() Ming Lei
2019-08-13 8:14 ` [PATCH V3 3/3] genirq/affinity: Spread vectors on node according to nr_cpu ratio Ming Lei
2019-08-13 9:34 ` Daniel Wagner
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=20190813081447.1396-1-ming.lei@redhat.com \
--to=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).