From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH for-next 7/7] RDMA/bnxt_re: Enable congestion control by default
Date: Wed, 29 Mar 2023 10:23:39 +0300 [thread overview]
Message-ID: <20230329072339.GD831478@unreal> (raw)
In-Reply-To: <1679562739-24472-8-git-send-email-selvin.xavier@broadcom.com>
On Thu, Mar 23, 2023 at 02:12:19AM -0700, Selvin Xavier wrote:
> Enable Congesion control by default. Issue FW command
> enable the CC during driver load and disable it during
> unload.
>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/main.c | 24 ++++++-
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.c | 15 ++--
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.h | 20 ++++--
> drivers/infiniband/hw/bnxt_re/qplib_sp.c | 109 +++++++++++++++++++++++++++++
> drivers/infiniband/hw/bnxt_re/qplib_sp.h | 67 ++++++++++++++++++
> 5 files changed, 222 insertions(+), 13 deletions(-)
<...>
> index 06979f7..73f936c 100644
> --- a/drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
> +++ b/drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
> @@ -96,7 +96,7 @@ static int __send_message(struct bnxt_qplib_rcfw *rcfw,
> u32 sw_prod, cmdq_prod;
> struct pci_dev *pdev;
> unsigned long flags;
> - u32 size, opcode;
> + u32 bsize, opcode;
> u16 cookie, cbit;
> u8 *preq;
<...>
> memset(msg->resp, 0, sizeof(*msg->resp));
> crsqe->resp = (struct creq_qp_event *)msg->resp;
> - crsqe->resp->cookie = msg->req->cookie;
> + crsqe->resp->cookie = cookie;
I see that you didn't change cookie type in this patch, but it is better
to fix smatch/sparse warnings while you are changing the code.
I don't want to see any warnings generated by new patches even for old code.
drivers/infiniband/hw/bnxt_re/qplib_rcfw.c:155:29: warning: incorrect type in assignment (different base types)
drivers/infiniband/hw/bnxt_re/qplib_rcfw.c:155:29: expected restricted __le16 [usertype] cookie
drivers/infiniband/hw/bnxt_re/qplib_rcfw.c:155:29: got unsigned short [assigned] [usertype] cookie
drivers/infiniband/hw/bnxt_re/qplib_rcfw.h:96:13: warning: restricted __le16 degrades to integer
Thanks
next prev parent reply other threads:[~2023-03-29 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:12 [PATCH for-next 0/7] RDMA/bnxt_re: Enable Congestion control by default Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 1/7] RDMA/bnxt_re: Update HW interface headers Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 2/7] RDMA/bnxt_re: Remove HW queue mapping from RoCE Driver Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 3/7] RDMA/bnxt_re: Convert RCFW_CMD_PREP macro to static inline function Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 4/7] RDMA/bnxt_re: Reduce number of argumets to control path command APIs Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 5/7] RDMA/bnxt_re: RoCE slow path TLV support Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 6/7] RDAM/bnxt_re: Use tlv apis while processing the slow path commands Selvin Xavier
2023-03-23 9:12 ` [PATCH for-next 7/7] RDMA/bnxt_re: Enable congestion control by default Selvin Xavier
2023-03-23 11:01 ` kernel test robot
2023-03-29 7:23 ` Leon Romanovsky [this message]
2023-03-29 9:31 ` Selvin Xavier
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=20230329072339.GD831478@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@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