From: Tariq Toukan <tariqt@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>, <linux-rdma@vger.kernel.org>,
"Mark Bloch" <mbloch@nvidia.com>, <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Gal Pressman <gal@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Moshe Shemesh <moshe@nvidia.com>, Nimrod Oren <noren@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>, Shay Drory <shayd@nvidia.com>
Subject: [PATCH mlx5-next 1/2] net/mlx5: Add cap_tx_speed and effective_tx_speed support to IFC
Date: Mon, 5 Oct 2026 11:40:46 +0300 [thread overview]
Message-ID: <20261005084047.237081-2-tariqt@nvidia.com> (raw)
In-Reply-To: <20261005084047.237081-1-tariqt@nvidia.com>
From: Or Har-Toov <ohartoov@nvidia.com>
Introduce the cap_tx_speed and effective_tx_speed fields to the query
and modify_vport_state structures.
Add the esw_vport_state_cap_tx_speed and
esw_vport_state_effective_tx_speed capability bits, indicating the
firmware supports modifying the cap_tx_speed and effective_tx_speed
fields, via the MODIFY_VPORT_STATE command.
Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Nimrod Oren <noren@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
---
include/linux/mlx5/mlx5_ifc.h | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h
index a712463e89b4..989408764e1b 100644
--- a/include/linux/mlx5/mlx5_ifc.h
+++ b/include/linux/mlx5/mlx5_ifc.h
@@ -1070,7 +1070,9 @@ struct mlx5_ifc_e_switch_cap_bits {
u8 root_ft_on_other_esw[0x1];
u8 reserved_at_a[0x1];
u8 esw_vport_state_max_tx_speed[0x1];
- u8 reserved_at_c[0xd];
+ u8 esw_vport_state_cap_tx_speed[0x1];
+ u8 esw_vport_state_effective_tx_speed[0x1];
+ u8 reserved_at_e[0xb];
u8 esw_functions_changed[0x1];
u8 reserved_at_1a[0x1];
u8 ecpf_vport_exists[0x1];
@@ -5492,6 +5494,9 @@ struct mlx5_ifc_query_vport_state_out_bits {
u8 reserved_at_70[0x8];
u8 admin_state[0x4];
u8 state[0x4];
+
+ u8 cap_tx_speed[0x10];
+ u8 effective_tx_speed[0x10];
};
struct mlx5_ifc_array1024_auto_bits {
@@ -7840,6 +7845,9 @@ struct mlx5_ifc_modify_vport_state_in_bits {
u8 reserved_at_74[0x4];
u8 admin_state[0x4];
u8 reserved_at_7c[0x4];
+
+ u8 cap_tx_speed[0x10];
+ u8 effective_tx_speed[0x10];
};
struct mlx5_ifc_modify_tis_out_bits {
--
2.44.0
next prev parent reply other threads:[~2026-10-05 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 8:40 [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05 Tariq Toukan
2026-10-05 8:40 ` Tariq Toukan [this message]
2026-10-05 8:40 ` [PATCH mlx5-next 2/2] net/mlx5: IFC, Add capability bits for virtual LAG Tariq Toukan
2026-10-05 13:29 ` [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05 Przemek Kitszel
2026-10-05 21:24 ` Jakub Kicinski
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=20261005084047.237081-2-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@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=noren@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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®