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, kashyap.desai@broadcom.com
Subject: Re: [PATCH v2 for-next 00/17] RDMA/bnxt_re: Control path updates
Date: Mon, 12 Jun 2023 10:12:32 +0300 [thread overview]
Message-ID: <20230612071232.GQ12152@unreal> (raw)
In-Reply-To: <1686308514-11996-1-git-send-email-selvin.xavier@broadcom.com>
On Fri, Jun 09, 2023 at 04:01:37AM -0700, Selvin Xavier wrote:
> This patch series from Kashyap includes code refactoring and some
> optimizations in the FW control path of the driver. It also address
> some of the issues seen as we scale up the HW resources.
> It also includes few bug fixes in the control path.
>
> Please review and apply.
>
> Thanks,
> Selvin Xavier
>
> v1 -> v2:
> - Fix the warning reported by kbuild test robot in patch 10 about
> variables set and not used. Rebased the other patches based on
> the modified patch.
> - Reported-by: kernel test robot <lkp@intel.com>
>
> Kashyap Desai (17):
> RDMA/bnxt_re: wraparound mbox producer index
> RDMA/bnxt_re: Avoid calling wake_up threads from spin_lock context
> RDMA/bnxt_re: remove virt_func check while creating RoCE FW channel
> RDMA/bnxt_re: set fixed command queue depth
> RDMA/bnxt_re: Enhance the existing functions that wait for FW
> responses
> RDMA/bnxt_re: Avoid the command wait if firmware is inactive
> RDMA/bnxt_re: use shadow qd while posting non blocking rcfw command
> RDMA/bnxt_re: Simplify the function that sends the FW commands
> RDMA/bnxt_re: add helper function __poll_for_resp
> RDMA/bnxt_re: handle command completions after driver detect a
> timedout
> RDMA/bnxt_re: Add firmware stall check detection
> RDMA/bnxt_re: post destroy_ah for delayed completion of AH creation
> RDMA/bnxt_re: consider timeout of destroy ah as success.
> RDMA/bnxt_re: cancel all control path command waiters upon error.
> RDMA/bnxt_re: use firmware provided max request timeout
> RDMA/bnxt_re: remove redundant cmdq_bitmap
> RDMA/bnxt_re: optimize the parameters passed to helper functions
I applied whole series as is. It looks good enough, but please address
my concern about atomit_t.
Thanks
>
> drivers/infiniband/hw/bnxt_re/bnxt_re.h | 2 +
> drivers/infiniband/hw/bnxt_re/ib_verbs.c | 16 +-
> drivers/infiniband/hw/bnxt_re/main.c | 11 +-
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.c | 627 ++++++++++++++++++++++-------
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.h | 51 ++-
> drivers/infiniband/hw/bnxt_re/qplib_res.h | 1 +
> drivers/infiniband/hw/bnxt_re/qplib_sp.c | 8 +-
> drivers/infiniband/hw/bnxt_re/qplib_sp.h | 4 +-
> 8 files changed, 557 insertions(+), 163 deletions(-)
>
> --
> 2.5.5
>
next prev parent reply other threads:[~2023-06-12 7:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:01 [PATCH v2 for-next 00/17] RDMA/bnxt_re: Control path updates Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 01/17] RDMA/bnxt_re: wraparound mbox producer index Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 02/17] RDMA/bnxt_re: Avoid calling wake_up threads from spin_lock context Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 03/17] RDMA/bnxt_re: remove virt_func check while creating RoCE FW channel Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 04/17] RDMA/bnxt_re: set fixed command queue depth Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 05/17] RDMA/bnxt_re: Enhance the existing functions that wait for FW responses Selvin Xavier
2023-06-12 7:00 ` Leon Romanovsky
2023-06-09 11:01 ` [PATCH v2 for-next 06/17] RDMA/bnxt_re: Avoid the command wait if firmware is inactive Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 07/17] RDMA/bnxt_re: use shadow qd while posting non blocking rcfw command Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 08/17] RDMA/bnxt_re: Simplify the function that sends the FW commands Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 09/17] RDMA/bnxt_re: add helper function __poll_for_resp Selvin Xavier
2023-06-12 7:04 ` Leon Romanovsky
2023-06-12 8:01 ` Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 10/17] RDMA/bnxt_re: handle command completions after driver detect a timedout Selvin Xavier
2023-06-12 7:07 ` Leon Romanovsky
2023-06-09 11:01 ` [PATCH v2 for-next 11/17] RDMA/bnxt_re: Add firmware stall check detection Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 12/17] RDMA/bnxt_re: post destroy_ah for delayed completion of AH creation Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 13/17] RDMA/bnxt_re: consider timeout of destroy ah as success Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 14/17] RDMA/bnxt_re: cancel all control path command waiters upon error Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 15/17] RDMA/bnxt_re: use firmware provided max request timeout Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 16/17] RDMA/bnxt_re: remove redundant cmdq_bitmap Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 17/17] RDMA/bnxt_re: optimize the parameters passed to helper functions Selvin Xavier
2023-06-12 7:12 ` Leon Romanovsky [this message]
2023-06-12 7:12 ` [PATCH v2 for-next 00/17] RDMA/bnxt_re: Control path updates Leon Romanovsky
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=20230612071232.GQ12152@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kashyap.desai@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).