DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com,
	Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>,
	Lance Richardson <lance.richardson@broadcom.com>
Subject: [dpdk-dev] [PATCH 2/7] net/bnxt: use correct number of RSS contexts for thor
Date: Fri, 19 Jul 2019 11:49:01 +0530	[thread overview]
Message-ID: <20190719061906.42451-3-ajit.khaparde@broadcom.com> (raw)
In-Reply-To: <20190719061906.42451-1-ajit.khaparde@broadcom.com>

From: Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>

BCM57500-based adapters use a variable number of RSS contexts
depending upon the number of receive rings in use. The current
implementation is erroneously using the maximum possible number
of RSS contexts instead of the actual number allocated when
setting up RSS tables in the adapter. Fix by using the actual
number of allocated contexts.

Fixes: 38412304b50a ("net/bnxt: enable RSS for thor-based controllers")

Reviewed-by: Lance Richardson <lance.richardson@broadcom.com>
Signed-off-by: Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>
Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
 drivers/net/bnxt/bnxt_hwrm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/bnxt/bnxt_hwrm.c b/drivers/net/bnxt/bnxt_hwrm.c
index 67b5ff661..692c6c399 100644
--- a/drivers/net/bnxt/bnxt_hwrm.c
+++ b/drivers/net/bnxt/bnxt_hwrm.c
@@ -1736,7 +1736,7 @@ bnxt_hwrm_vnic_rss_cfg_thor(struct bnxt *bp, struct bnxt_vnic_info *vnic)
 {
 	int i;
 	int rc = 0;
-	int nr_ctxs = bp->max_ring_grps;
+	int nr_ctxs = vnic->num_lb_ctxts;
 	struct hwrm_vnic_rss_cfg_input req = {.req_type = 0 };
 	struct hwrm_vnic_rss_cfg_output *resp = bp->hwrm_cmd_resp_addr;
 
-- 
2.20.1 (Apple Git-117)


  parent reply	other threads:[~2019-07-19  6:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  6:18 [dpdk-dev] [PATCH 0/7] bnxt patches Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 1/7] net/bnxt: add new device id Ajit Khaparde
2019-07-19  6:19 ` Ajit Khaparde [this message]
2019-07-19 21:38   ` [dpdk-dev] [PATCH 2/7] net/bnxt: use correct number of RSS contexts for thor Ferruh Yigit
2019-07-19  6:19 ` [dpdk-dev] [PATCH 3/7] net/bnxt: fix receive interrupt vector Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 4/7] net/bnxt: fix interrupt rearm logic Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 5/7] net/bnxt: disable vector mode Tx with VLAN offload Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 6/7] net/bnxt: remove unnecessary interrupt disable Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 7/7] doc: update release information for bnxt Ajit Khaparde
2019-07-19 21:38   ` Ferruh Yigit
2019-07-19 12:33 ` [dpdk-dev] [PATCH 0/7] bnxt patches Ferruh Yigit
2019-07-19 16:18   ` Stephen Hemminger
2019-07-19 16:58     ` Ferruh Yigit
2019-07-19 21:39 ` Ferruh Yigit

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=20190719061906.42451-3-ajit.khaparde@broadcom.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lance.richardson@broadcom.com \
    --cc=santosh.rastapur@broadcom.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).