linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Gurtovoy <maxg@mellanox.com>
To: linux-rdma@vger.kernel.org, jgg@mellanox.com, sagi@grimberg.me
Cc: vladimirk@mellanox.com, Max Gurtovoy <maxg@mellanox.com>,
	stable@vger.kernel.org, Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH 2/2] net/mlx5: fix affinity mask for completion vectors
Date: Mon,  5 Feb 2018 16:29:52 +0200	[thread overview]
Message-ID: <1517840992-29813-2-git-send-email-maxg@mellanox.com> (raw)
In-Reply-To: <1517840992-29813-1-git-send-email-maxg@mellanox.com>

Add an offset to ignore private mlx5 vectors.

Fixes: 05e0cc84e00c ("net/mlx5: Fix get vector affinity helper function")
Cc: <stable@vger.kernel.org>
Cc: Logan Gunthorpe <logang@deltatee.com>
Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
---
 include/linux/mlx5/driver.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/linux/mlx5/driver.h b/include/linux/mlx5/driver.h
index a061042..9bab9d3 100644
--- a/include/linux/mlx5/driver.h
+++ b/include/linux/mlx5/driver.h
@@ -1229,6 +1229,7 @@ enum {
 	MLX5_TRIGGERED_CMD_COMP = (u64)1 << 32,
 };
 
+/* Returns the affinity mask of a completion vector */
 static inline const struct cpumask *
 mlx5_get_vector_affinity(struct mlx5_core_dev *dev, int vector)
 {
@@ -1238,7 +1239,7 @@ enum {
 	int eqn;
 	int err;
 
-	err = mlx5_vector2eqn(dev, vector, &eqn, &irq);
+	err = mlx5_vector2eqn(dev, MLX5_EQ_VEC_COMP_BASE + vector, &eqn, &irq);
 	if (err)
 		return NULL;
 
-- 
1.8.3.1

  reply	other threads:[~2018-02-05 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 14:29 [PATCH 1/2] net/mlx5: increase async EQ to avoid EQ overrun Max Gurtovoy
2018-02-05 14:29 ` Max Gurtovoy [this message]
2018-02-05 14:36   ` [PATCH 2/2] net/mlx5: fix affinity mask for completion vectors Sagi Grimberg
     [not found] ` <1517840992-29813-1-git-send-email-maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 15:28   ` [PATCH 1/2] net/mlx5: increase async EQ to avoid EQ overrun Sagi Grimberg
2018-02-05 16:02   ` Doug Ledford
     [not found]     ` <1517846530.3936.71.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-02-05 16:10       ` Leon Romanovsky
2018-02-05 18:09   ` Jason Gunthorpe
     [not found]     ` <20180205180904.GB11446-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 23:11       ` Max Gurtovoy
     [not found]         ` <d572b570-0844-e441-19a0-e6804557fb58-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-05 23:16           ` Jason Gunthorpe
     [not found]             ` <20180205231617.GQ11446-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-08  5:45               ` Saeed Mahameed
     [not found]                 ` <CALzJLG9QQ_B4xj-E+HtpxUWZhFU9eWeqSNHSaQjf5HH=9TPXTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-08 16:26                   ` Jason Gunthorpe
     [not found]                     ` <20180208162605.GK9051-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-08 16:39                       ` Leon Romanovsky
2018-02-08 18:58                       ` Saeed Mahameed

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=1517840992-29813-2-git-send-email-maxg@mellanox.com \
    --to=maxg@mellanox.com \
    --cc=jgg@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sagi@grimberg.me \
    --cc=stable@vger.kernel.org \
    --cc=vladimirk@mellanox.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).