From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: 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>,
Saeed Mahameed <saeed@kernel.org>, Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Feng Liu <feliu@nvidia.com>
Subject: Re: [PATCH net-next V2 2/2] net/mlx5e: Expose TIS via devlink tx reporter diagnose
Date: Wed, 23 Jul 2025 08:56:49 +0200 [thread overview]
Message-ID: <aICHsQPoI+gO3eTQ@mev-dev.igk.intel.com> (raw)
In-Reply-To: <1753194228-333722-3-git-send-email-tariqt@nvidia.com>
On Tue, Jul 22, 2025 at 05:23:48PM +0300, Tariq Toukan wrote:
> From: Feng Liu <feliu@nvidia.com>
>
> Underneath "TIS Config" tag expose TIS diagnostic information.
> Expose the tisn of each TC under each lag port.
>
> $ sudo devlink health diagnose auxiliary/mlx5_core.eth.2/131072 reporter tx
> ......
> TIS Config:
> lag port: 0 tc: 0 tisn: 0
> lag port: 1 tc: 0 tisn: 8
> ......
>
> Signed-off-by: Feng Liu <feliu@nvidia.com>
> Reviewed-by: Aya Levin <ayal@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
> ---
> .../mellanox/mlx5/core/en/reporter_tx.c | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c b/drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c
> index bd96988e102c..85d5cb39b107 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c
> @@ -311,6 +311,30 @@ mlx5e_tx_reporter_diagnose_common_config(struct devlink_health_reporter *reporte
> mlx5e_health_fmsg_named_obj_nest_end(fmsg);
> }
>
> +static void
> +mlx5e_tx_reporter_diagnose_tis_config(struct devlink_health_reporter *reporter,
> + struct devlink_fmsg *fmsg)
> +{
> + struct mlx5e_priv *priv = devlink_health_reporter_priv(reporter);
> + u8 num_tc = mlx5e_get_dcb_num_tc(&priv->channels.params);
> + u32 tc, i, tisn;
> +
> + devlink_fmsg_arr_pair_nest_start(fmsg, "TIS Config");
> + for (i = 0; i < mlx5e_get_num_lag_ports(priv->mdev); i++) {
> + for (tc = 0; tc < num_tc; tc++) {
nit: tisn can be defined in this for, not outside.
> + tisn = mlx5e_profile_get_tisn(priv->mdev, priv,
> + priv->profile, i, tc);
> +
> + devlink_fmsg_obj_nest_start(fmsg);
> + devlink_fmsg_u32_pair_put(fmsg, "lag port", i);
> + devlink_fmsg_u32_pair_put(fmsg, "tc", tc);
> + devlink_fmsg_u32_pair_put(fmsg, "tisn", tisn);
> + devlink_fmsg_obj_nest_end(fmsg);
> + }
> + }
> + devlink_fmsg_arr_pair_nest_end(fmsg);
> +}
> +
> static int mlx5e_tx_reporter_diagnose(struct devlink_health_reporter *reporter,
> struct devlink_fmsg *fmsg,
> struct netlink_ext_ack *extack)
> @@ -326,6 +350,7 @@ static int mlx5e_tx_reporter_diagnose(struct devlink_health_reporter *reporter,
> goto unlock;
>
> mlx5e_tx_reporter_diagnose_common_config(reporter, fmsg);
> + mlx5e_tx_reporter_diagnose_tis_config(reporter, fmsg);
> devlink_fmsg_arr_pair_nest_start(fmsg, "SQs");
> for (i = 0; i < priv->channels.num; i++) {
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> --
> 2.31.1
next prev parent reply other threads:[~2025-07-23 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:23 [PATCH net-next V2 0/2] net/mlx5e: misc changes 2025-07-22 Tariq Toukan
2025-07-22 14:23 ` [PATCH net-next V2 1/2] net/mlx5e: Support routed networks during IPsec MACs initialization Tariq Toukan
2025-07-23 6:52 ` Michal Swiatkowski
2025-07-23 7:10 ` Leon Romanovsky
2025-07-22 14:23 ` [PATCH net-next V2 2/2] net/mlx5e: Expose TIS via devlink tx reporter diagnose Tariq Toukan
2025-07-23 6:56 ` Michal Swiatkowski [this message]
2025-07-25 23:26 ` [PATCH net-next V2 0/2] net/mlx5e: misc changes 2025-07-22 patchwork-bot+netdevbpf
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=aICHsQPoI+gO3eTQ@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=feliu@nvidia.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@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 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®