From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com,
michael.chan@broadcom.com
Subject: Re: [PATCH for-next v2 0/7]RDMA/bnxt_re: Doorbell Drop Prevention
Date: Tue, 18 Jul 2023 12:40:27 +0300 [thread overview]
Message-ID: <20230718094027.GB8808@unreal> (raw)
In-Reply-To: <1689573194-27687-1-git-send-email-selvin.xavier@broadcom.com>
On Sun, Jul 16, 2023 at 10:53:07PM -0700, Selvin Xavier wrote:
> The idea behind this series is to prevent Doorbell drops
> on some of the Broadcom adapters that require Doorbell
> moderation. This is achieved by pacing the doorbell writes
> into the hardware FIFO. The rate at which individual doorbells
> are written needs to be dynamically adjusted, because
> it depends on the ability of the hardware to drain the
> FIFO and on the number and behavior of individual
> doorbell writers. When congestion is detected by the user
> library, it notifies the driver and driver adjust the
> pacing parameters dynamically in a shared page, which will
> be used for pacing the Doorbells.
>
> Currently this feature is targeted only for user applications.
> The corresponding user lib patch is in the pull request.
> https://github.com/linux-rdma/rdma-core/pull/1360
>
> Thanks,
> Selivn
>
> v1 -> v2:
> Rebased the patches on top of the latest for-next branch
>
> Chandramohan Akula (7):
> bnxt_en: Update HW interface headers
> bnxt_en: Share the bar0 address with the RoCE driver
> RDMA/bnxt_re: Initialize Doorbell pacing feature
> RDMA/bnxt_re: Enable pacing support for the user apps
> RDMA/bnxt_re: Update alloc_page uapi for pacing
> RDMA/bnxt_re: Implement doorbell pacing algorithm
> RDMA/bnxt_re: Add a new uapi for driver notification
Jason, any comments?
Thanks
>
> drivers/infiniband/hw/bnxt_re/bnxt_re.h | 27 ++++
> drivers/infiniband/hw/bnxt_re/ib_verbs.c | 51 +++++-
> drivers/infiniband/hw/bnxt_re/ib_verbs.h | 2 +
> drivers/infiniband/hw/bnxt_re/main.c | 220 ++++++++++++++++++++++++++
> drivers/infiniband/hw/bnxt_re/qplib_res.h | 19 +++
> drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h | 54 +++++++
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 2 +-
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h | 1 +
> include/uapi/rdma/bnxt_re-abi.h | 7 +
> 9 files changed, 379 insertions(+), 4 deletions(-)
>
> --
> 2.5.5
>
prev parent reply other threads:[~2023-07-18 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 5:53 [PATCH for-next v2 0/7]RDMA/bnxt_re: Doorbell Drop Prevention Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 1/7] bnxt_en: Update HW interface headers Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 2/7] bnxt_en: Share the bar0 address with the RoCE driver Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 3/7] RDMA/bnxt_re: Initialize Doorbell pacing feature Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 4/7] RDMA/bnxt_re: Enable pacing support for the user apps Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 5/7] RDMA/bnxt_re: Update alloc_page uapi for pacing Selvin Xavier
2023-07-18 23:16 ` kernel test robot
2023-07-17 5:53 ` [PATCH for-next v2 6/7] RDMA/bnxt_re: Implement doorbell pacing algorithm Selvin Xavier
2023-07-17 5:53 ` [PATCH for-next v2 7/7] RDMA/bnxt_re: Add a new uapi for driver notification Selvin Xavier
2023-07-18 9:40 ` Leon Romanovsky [this message]
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=20230718094027.GB8808@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--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