From: Yongseok Koh <yskoh@mellanox.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: Scott Branden <scott.branden@broadcom.com>,
Randy Schacher <stuart.schacher@broadcom.com>,
dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] patch 'net/bnxt: fix RETA size' has been queued to LTS release 17.11.4
Date: Mon, 13 Aug 2018 13:40:06 -0700 [thread overview]
Message-ID: <20180813204010.25281-6-yskoh@mellanox.com> (raw)
In-Reply-To: <20180813204010.25281-1-yskoh@mellanox.com>
Hi,
FYI, your patch has been queued to LTS release 17.11.4
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 08/15/18. So please
shout if anyone has objections.
Thanks.
Yongseok
---
>From 2658600aca85843080ca6ae6f0afb4f08e065c50 Mon Sep 17 00:00:00 2001
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wed, 25 Jul 2018 18:15:48 -0700
Subject: [PATCH] net/bnxt: fix RETA size
[ upstream commit 7f675c27d9c80bc6ff3793140fa3215671b295d6 ]
The reta_size being indicated in the bnxt_dev_info_get_op was incorrect.
Set it to the value supported by the hardware.
Fixes: 0a6d2a720078 ("net/bnxt: get device infos")
Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Reviewed-by: Scott Branden <scott.branden@broadcom.com>
Reviewed-by: Randy Schacher <stuart.schacher@broadcom.com>
Tested-by: Randy Schacher <stuart.schacher@broadcom.com>
---
drivers/net/bnxt/bnxt_ethdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
index 5b0bf80e3..7466a642e 100644
--- a/drivers/net/bnxt/bnxt_ethdev.c
+++ b/drivers/net/bnxt/bnxt_ethdev.c
@@ -440,7 +440,7 @@ static void bnxt_dev_info_get_op(struct rte_eth_dev *eth_dev,
/* For the sake of symmetry, max_rx_queues = max_tx_queues */
dev_info->max_rx_queues = max_rx_rings;
dev_info->max_tx_queues = max_rx_rings;
- dev_info->reta_size = bp->max_rsscos_ctx;
+ dev_info->reta_size = HW_HASH_INDEX_SIZE;
dev_info->hash_key_size = 40;
max_vnics = bp->max_vnics;
--
2.11.0
next prev parent reply other threads:[~2018-08-13 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 20:40 [dpdk-stable] patch 'net/octeontx: fix stop clearing Rx/Tx functions' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/bnxt: fix filter freeing' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/bnxt: fix memory leaks in NVM commands' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/bnxt: fix lock release on NVM write failure' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/bnxt: check access denied for HWRM commands' " Yongseok Koh
2018-08-13 20:40 ` Yongseok Koh [this message]
2018-08-13 20:40 ` [dpdk-stable] patch 'net/qede: fix interrupt handler unregister' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/qede/base: fix GRC attention callback' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/qede: fix MAC address removal failure message' " Yongseok Koh
2018-08-13 20:40 ` [dpdk-stable] patch 'net/bnx2x: fix FW command timeout during stop' " Yongseok Koh
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=20180813204010.25281-6-yskoh@mellanox.com \
--to=yskoh@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@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).