From: Leon Romanovsky <leon@kernel.org>
To: Max Makarov <makarov@volta.cloud>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
saeedm@nvidia.com, tariqt@nvidia.com, mbloch@nvidia.com
Subject: Re: [QUESTION] mlx5: format_select_dw_8_6_ext capability on ConnectX-7
Date: Tue, 19 May 2026 17:37:04 +0300 [thread overview]
Message-ID: <20260519143704.GY33515@unreal> (raw)
In-Reply-To: <177912266235.29998.14244693862353385829@volta.cloud>
On Tue, May 19, 2026 at 01:44:22AM +0900, Max Makarov wrote:
> Hi,
>
> Question about the cmd_hca_cap_2.format_select_dw_8_6_ext bit (introduced
> into mlx5_ifc.h in v6.12-rc1).
>
> On all three of our standalone ConnectX-7 SKUs (PSIDs MT_0000000838,
> MT_0000000840, MT_0000000892, firmware 28.48.1000) this bit reads as 0 in
> both GET_CUR and GET_MAX modes. The DPDK code at
> drivers/net/mlx5/hws/mlx5dr_cmd.c reads it without any device-ID
> conditional, so it appears to be exclusively firmware-controlled — yet
> firmware reports 0 across all our CX-7 cards, including the latest
> public release.
>
> This blocks DOCA Flow CT pipe for IPv6 (which requires the 11-DW jumbo
> STE format gated by this bit).
>
> Two questions:
>
> 1. Is the kernel's filter that rejects SET_HCA_CAP for cap_class !=
> MLX5_CAP_GENERAL intentional? If so, what's the rationale?
>
> 2. From the NVIDIA side: is this capability hardware-fused on standalone
> CX-7 (BlueField-3 advertises it as 1), or could a future firmware
> release enable it on CX-7?
Please contact your NVIDIA support representative.
Thanks
>
> Thanks,
> Max Makarov
> Volta Cloud
>
prev parent reply other threads:[~2026-05-19 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 16:44 [QUESTION] mlx5: format_select_dw_8_6_ext capability on ConnectX-7 Max Makarov
2026-05-19 14:37 ` 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=20260519143704.GY33515@unreal \
--to=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=makarov@volta.cloud \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.