From: dwagner@suse.de (Daniel Wagner)
Subject: [PATCH V3 3/3] genirq/affinity: Spread vectors on node according to nr_cpu ratio
Date: Tue, 13 Aug 2019 11:34:27 +0200 [thread overview]
Message-ID: <7579c5b8-3992-e685-d559-98e9b0f7baad@suse.de> (raw)
In-Reply-To: <20190813081447.1396-4-ming.lei@redhat.com>
Hi,
On 8/13/19 10:14 AM, Ming Lei wrote:
> Now __irq_build_affinity_masks() spreads vectors evenly per node, and
> all vectors may not be spread in case that each numa node has different
> CPU number, then the following warning in irq_build_affinity_masks() can
> be triggered:
>
> if (nr_present < numvecs)
> WARN_ON(nr_present + nr_others < numvecs);
Is this the warning which is changed in patch #1?
Thanks,
Daniel
prev parent reply other threads:[~2019-08-13 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 8:14 [PATCH V3 0/3] genriq/affinity: Make vectors allocation fair Ming Lei
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 [this message]
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=7579c5b8-3992-e685-d559-98e9b0f7baad@suse.de \
--to=dwagner@suse.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