From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: Jay Ding <jay.ding@broadcom.com>,
stable@dpdk.org, Randy Schacher <stuart.schacher@broadcom.com>
Subject: [dpdk-dev] [PATCH 1/2] net/bnxt: fix resource qcap list handling
Date: Thu, 29 Jul 2021 22:36:11 -0700 [thread overview]
Message-ID: <20210730053612.3374-2-ajit.khaparde@broadcom.com> (raw)
In-Reply-To: <20210730053612.3374-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
From: Jay Ding <jay.ding@broadcom.com>
The size of resource qcap list could be different when FW
and application are not match. Application should be able
to handle it when the FW is older and the size of qcap is
smaller.
This patch is needed for backward compatibility on older
firmware versions.
Fixes: 873661aa641a1 ("net/bnxt: support shared session")
Cc: stable@dpdk.org
Signed-off-by: Jay Ding <jay.ding@broadcom.com>
Reviewed-by: Randy Schacher <stuart.schacher@broadcom.com>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
drivers/net/bnxt/tf_core/tf_msg.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/net/bnxt/tf_core/tf_msg.c b/drivers/net/bnxt/tf_core/tf_msg.c
index 6717710dbd..e07d9168be 100644
--- a/drivers/net/bnxt/tf_core/tf_msg.c
+++ b/drivers/net/bnxt/tf_core/tf_msg.c
@@ -440,18 +440,18 @@ tf_msg_session_resc_qcaps(struct tf *tfp,
* Should always get expected number of entries
*/
if (tfp_le_to_cpu_32(resp.size) != size) {
- TFP_DRV_LOG(ERR,
- "%s: QCAPS message size error, rc:%s\n",
+ TFP_DRV_LOG(WARNING,
+ "%s: QCAPS message size error, rc:%s, request %d vs response %d\n",
tf_dir_2_str(dir),
- strerror(EINVAL));
- rc = -EINVAL;
- goto cleanup;
+ strerror(EINVAL),
+ size,
+ resp.size);
}
/* Post process the response */
data = (struct tf_rm_resc_req_entry *)qcaps_buf.va_addr;
- for (i = 0; i < size; i++) {
+ for (i = 0; i < resp.size; i++) {
query[i].type = tfp_le_to_cpu_32(data[i].type);
query[i].min = tfp_le_to_cpu_16(data[i].min);
query[i].max = tfp_le_to_cpu_16(data[i].max);
--
2.21.1 (Apple Git-122.3)
next prev parent reply other threads:[~2021-07-30 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 5:36 [dpdk-dev] [PATCH 0/2] fixes to bnxt PMD Ajit Khaparde
2021-07-30 5:36 ` Ajit Khaparde [this message]
2021-07-30 5:36 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix stats counter resource Ajit Khaparde
2021-07-30 14:14 ` [dpdk-dev] [PATCH 0/2] fixes to bnxt PMD Ajit Khaparde
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=20210730053612.3374-2-ajit.khaparde@broadcom.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=jay.ding@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).