From: Leon Romanovsky <leon@kernel.org>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
Subject: Re: [PATCH rdma-rext V2 1/5] IB/core: Extend rate limit support for RC QPs
Date: Sun, 1 Feb 2026 14:51:25 +0200 [thread overview]
Message-ID: <20260201125125.GB34749@unreal> (raw)
In-Reply-To: <20260129102133.2878811-2-kalesh-anakkur.purayil@broadcom.com>
On Thu, Jan 29, 2026 at 03:51:29PM +0530, Kalesh AP wrote:
> Broadcom devices supports setting the rate limit while changing
> RC QP state from INIT to RTR, RTR to RTS and RTS to RTS.
>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
> ---
> drivers/infiniband/core/verbs.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
This patch should be the last in the series. We must first add driver
support, then address the required fixes in the mlx5 driver, and only
after that expose this functionality to users.
Thanks
>
> diff --git a/drivers/infiniband/core/verbs.c b/drivers/infiniband/core/verbs.c
> index 8b56b6b62352..02ebc3e52196 100644
> --- a/drivers/infiniband/core/verbs.c
> +++ b/drivers/infiniband/core/verbs.c
> @@ -1537,7 +1537,8 @@ static const struct {
> IB_QP_PKEY_INDEX),
> [IB_QPT_RC] = (IB_QP_ALT_PATH |
> IB_QP_ACCESS_FLAGS |
> - IB_QP_PKEY_INDEX),
> + IB_QP_PKEY_INDEX |
> + IB_QP_RATE_LIMIT),
> [IB_QPT_XRC_INI] = (IB_QP_ALT_PATH |
> IB_QP_ACCESS_FLAGS |
> IB_QP_PKEY_INDEX),
> @@ -1585,7 +1586,8 @@ static const struct {
> IB_QP_ALT_PATH |
> IB_QP_ACCESS_FLAGS |
> IB_QP_MIN_RNR_TIMER |
> - IB_QP_PATH_MIG_STATE),
> + IB_QP_PATH_MIG_STATE |
> + IB_QP_RATE_LIMIT),
> [IB_QPT_XRC_INI] = (IB_QP_CUR_STATE |
> IB_QP_ALT_PATH |
> IB_QP_ACCESS_FLAGS |
> @@ -1619,7 +1621,8 @@ static const struct {
> IB_QP_ACCESS_FLAGS |
> IB_QP_ALT_PATH |
> IB_QP_PATH_MIG_STATE |
> - IB_QP_MIN_RNR_TIMER),
> + IB_QP_MIN_RNR_TIMER |
> + IB_QP_RATE_LIMIT),
> [IB_QPT_XRC_INI] = (IB_QP_CUR_STATE |
> IB_QP_ACCESS_FLAGS |
> IB_QP_ALT_PATH |
> --
> 2.43.5
>
next prev parent reply other threads:[~2026-02-01 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 10:21 [PATCH rdma-rext V2 0/5] RDMA/bnxt_re: Add QP rate limit support Kalesh AP
2026-01-29 10:21 ` [PATCH rdma-rext V2 1/5] IB/core: Extend rate limit support for RC QPs Kalesh AP
2026-02-01 12:51 ` Leon Romanovsky [this message]
2026-02-02 3:22 ` Kalesh Anakkur Purayil
2026-01-29 10:21 ` [PATCH rdma-rext V2 2/5] RDMA/bnxt_re: Add support for QP rate limiting Kalesh AP
2026-02-01 12:55 ` Leon Romanovsky
2026-01-29 10:21 ` [PATCH rdma-rext V2 3/5] RDMA/bnxt_re: Report packet pacing capabilities when querying device Kalesh AP
2026-01-29 10:21 ` [PATCH rdma-rext V2 4/5] RDMA/bnxt_re: Report QP rate limit in debugfs Kalesh AP
2026-01-29 10:21 ` [PATCH rdma-rext V2 5/5] RDMA/mlx5: Support rate limit only for Raw Packet QP Kalesh AP
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=20260201125125.GB34749@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=damodharam.ammepalli@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@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