From: Leon Romanovsky <leon@kernel.org>
To: Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Selvin Xavier <selvin.xavier@broadcom.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
Abhijit Gangurde <abhijit.gangurde@amd.com>,
Allen Hubbe <allen.hubbe@amd.com>,
Edward Srouji <edwards@nvidia.com>
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maher Sanalla <msanalla@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>
Subject: Re: [PATCH rdma-next 0/8] RDMA: Extend packet pacing support to UD and UC QPs
Date: Thu, 11 Jun 2026 07:06:13 -0400 [thread overview]
Message-ID: <178117597316.3200217.13896844622260724399.b4-ty@kernel.org> (raw)
In-Reply-To: <20260524-packet-pacing-v1-0-3d79439f8d08@nvidia.com>
On Sun, 24 May 2026 18:38:01 +0300, Edward Srouji wrote:
> The primary goal of this series is to extend mlx5 packet pacing (rate
> limit) beyond raw packet QPs to cover UD and UC QPs while keeping the
> IB core free of vendor-specific policy for non-standard modify
> attributes.
>
> Today, IB_QP_RATE_LIMIT is restricted by the IB core qp_state_table
> to RC QPs only. It is also the only non-standard modify QP attribute,
> but as rate limit support expands across vendors, and as additional
> non-standard attributes are likely to follow, centralizing such policy
> in the core becomes impractical. Each driver is better positioned to
> enforce its own supported QP types and transitions over non-standard
> attributes. The series therefore removes IB_QP_RATE_LIMIT from the
> qp_state_table and modifies the affected vendor drivers to validate the
> attribute locally, preserving their existing behavior.
>
> [...]
Applied, thanks!
[1/8] net/mlx5: Add UD and UC packet pacing caps
https://git.kernel.org/rdma/rdma/c/a7b8dac8881dc6
[2/8] RDMA/mlx5: Refactor raw packet QP rate limit handling
https://git.kernel.org/rdma/rdma/c/e1008f19fa977d
[3/8] RDMA/mlx5: Add support for rate limit in UD and UC QPs
https://git.kernel.org/rdma/rdma/c/29e0a014ddfbdb
[4/8] RDMA/mlx5: Support deferred rate limit configuration
https://git.kernel.org/rdma/rdma/c/915bbc8578e3f7
[5/8] RDMA/mlx5: Report packet pacing capabilities when querying device
https://git.kernel.org/rdma/rdma/c/1f307090e95750
[6/8] RDMA/bnxt_re: Validate rate limit attribute in modify QP
https://git.kernel.org/rdma/rdma/c/8cca27313636c3
[7/8] RDMA/ionic: Validate rate limit attribute in modify QP
https://git.kernel.org/rdma/rdma/c/c2cd90ab881c69
[8/8] IB/core: Delegate IB_QP_RATE_LIMIT validation to drivers
https://git.kernel.org/rdma/rdma/c/8b0c66fa058b34
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-06-11 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 15:38 Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 1/8] net/mlx5: Add UD and UC packet pacing caps Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 2/8] RDMA/mlx5: Refactor raw packet QP rate limit handling Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 3/8] RDMA/mlx5: Add support for rate limit in UD and UC QPs Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 4/8] RDMA/mlx5: Support deferred rate limit configuration Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 5/8] RDMA/mlx5: Report packet pacing capabilities when querying device Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 6/8] RDMA/bnxt_re: Validate rate limit attribute in modify QP Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 7/8] RDMA/ionic: " Edward Srouji
2026-05-24 15:38 ` [PATCH rdma-next 8/8] IB/core: Delegate IB_QP_RATE_LIMIT validation to drivers Edward Srouji
2026-06-11 11:06 ` 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=178117597316.3200217.13896844622260724399.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=edwards@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=selvin.xavier@broadcom.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®