From: Leon Romanovsky <leon@kernel.org>
To: Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>
Cc: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Gal Pressman <gal@nvidia.com>, Moshe Shemesh <moshe@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Alexei Lazar <alazar@nvidia.com>
Subject: Re: [PATCH mlx5-next] net/mlx5: Add IFC bits for extended ETS rate limit bandwidth value
Date: Tue, 13 Jan 2026 03:45:05 -0500 [thread overview]
Message-ID: <176829390536.417489.9284250472543536413.b4-ty@kernel.org> (raw)
In-Reply-To: <1768200608-1543180-1-git-send-email-tariqt@nvidia.com>
On Mon, 12 Jan 2026 08:50:08 +0200, Tariq Toukan wrote:
> Add hardware interface definitions to support extended bandwidth rate
> limiting in the QoS Enhanced Transmission Selection (ETS) configuration.
>
> The new fields include:
> - max_bw_value: extended from 8-bit to 16-bit in ets_tcn_config_reg,
> simplifying the implementation by using a single field instead of
> separate MSB/LSB fields.
> - qetcr_qshr_max_bw_val_msb: capability bit in qcam_qos_feature_cap_mask
> indicating device support for the extended 16-bit max_bw_value field.
>
> [...]
Applied, thanks!
[1/1] net/mlx5: Add IFC bits for extended ETS rate limit bandwidth value
https://git.kernel.org/rdma/rdma/c/49e41f3ea3f754
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-01-13 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 6:50 Tariq Toukan
2026-01-13 8:45 ` 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=176829390536.417489.9284250472543536413.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=alazar@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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®