From: Andrei Vagin <avagin@virtuozzo.com>
To: <keith.busch@intel.com>, <hpa@zytor.com>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <mingo@kernel.org>
Cc: <linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:irq/urgent] genirq/affinity: Fix calculating vectors to assign
Date: Fri, 21 Apr 2017 21:37:22 -0700 [thread overview]
Message-ID: <20170422043721.GE2750@outlook.office365.com> (raw)
In-Reply-To: <tip-b72f8051f34b8164a62391e3676edc34523c5952@git.kernel.org>
Looks like 4.11 will be release in a few days, it would be nice if this
commit reaches the upstream tree before this moment.
Thanks.
On Thu, Apr 20, 2017 at 07:06:49AM -0700, tip-bot for Keith Busch wrote:
> Commit-ID: b72f8051f34b8164a62391e3676edc34523c5952
> Gitweb: http://git.kernel.org/tip/b72f8051f34b8164a62391e3676edc34523c5952
> Author: Keith Busch <keith.busch@intel.com>
> AuthorDate: Wed, 19 Apr 2017 19:51:10 -0400
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Thu, 20 Apr 2017 16:03:09 +0200
>
> genirq/affinity: Fix calculating vectors to assign
>
> The vectors_per_node is calculated from the remaining available vectors.
> The current vector starts after pre_vectors, so we need to subtract that
> from the current to properly account for the number of remaining vectors
> to assign.
>
> Fixes: 3412386b531 ("irq/affinity: Fix extra vecs calculation")
> Reported-by: Andrei Vagin <avagin@virtuozzo.com>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> Link: http://lkml.kernel.org/r/1492645870-13019-1-git-send-email-keith.busch@intel.com
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> ---
> kernel/irq/affinity.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/irq/affinity.c b/kernel/irq/affinity.c
> index d052947..e2d356d 100644
> --- a/kernel/irq/affinity.c
> +++ b/kernel/irq/affinity.c
> @@ -98,7 +98,7 @@ irq_create_affinity_masks(int nvecs, const struct irq_affinity *affd)
> int ncpus, v, vecs_to_assign, vecs_per_node;
>
> /* Spread the vectors per node */
> - vecs_per_node = (affv - curvec) / nodes;
> + vecs_per_node = (affv - (curvec - affd->pre_vectors)) / nodes;
>
> /* Get the cpus on this node which are in the mask */
> cpumask_and(nmsk, cpu_online_mask, cpumask_of_node(n));
prev parent reply other threads:[~2017-04-22 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 23:51 [PATCH] irq/affinity: " Keith Busch
2017-04-20 14:06 ` [tip:irq/urgent] genirq/affinity: " tip-bot for Keith Busch
2017-04-22 4:37 ` Andrei Vagin [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=20170422043721.GE2750@outlook.office365.com \
--to=avagin@virtuozzo.com \
--cc=hpa@zytor.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.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
all inboxes | Powered by JetHome®