From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org, tariqt@nvidia.com, saeedm@nvidia.com,
mbloch@nvidia.com, gal@nvidia.com, leon@kernel.org,
idosch@nvidia.com
Cc: alexanderduyck@fb.com, alok.a.tiwari@oracle.com,
andrew+netdev@lunn.ch, andrew@lunn.ch, davem@davemloft.net,
dg573847474@gmail.com, donald.hunter@gmail.com,
edumazet@google.com, horms@kernel.org, jacob.e.keller@intel.com,
kernel-team@meta.com, kory.maincent@bootlin.com, kuba@kernel.org,
lee@trager.us, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, linux@armlinux.org.uk,
mike.marciniszyn@gmail.com, o.rempel@pengutronix.de,
vadim.fedorenko@linux.dev, Mohsin Bashir <mohsin.bashr@gmail.com>
Subject: Re: [net-next V4 5/5] eth: mlx5: Move pause storm errors to pause stats
Date: Thu, 5 Mar 2026 12:26:13 +0100 [thread overview]
Message-ID: <f9fef510-09bb-44b5-8340-c472f3b95deb@redhat.com> (raw)
In-Reply-To: <20260302230149.1580195-6-mohsin.bashr@gmail.com>
On 3/3/26 12:01 AM, Mohsin Bashir wrote:
> Report device_stall_critical_watermark_cnt as tx_pause_storm_events in
> the ethtool_pause_stats struct. This counter tracks pause storm error
> events which indicate the NIC has been sending pause frames for an
> extended period due to a stall.
>
> The ethtool_pause_stats struct reports these stalls as a single value,
> whereas the device supports tracking them per priority. Aggregate the
> counter across all priority classes to capture stalls on all priorities.
> Note that the stats are fetched from the device for each priority via
> mlx5_core_access_reg().
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Mohsin Bashir <mohsin.bashr@gmail.com>
> ---
> .../ethernet/mellanox/mlx5/core/en_stats.c | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_stats.c b/drivers/net/ethernet/mellanox/mlx5/core/en_stats.c
> index a8af84fc9763..1a3ecf073913 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en_stats.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_stats.c
> @@ -916,11 +916,30 @@ static int mlx5e_stats_get_ieee(struct mlx5_core_dev *mdev,
> sz, MLX5_REG_PPCNT, 0, 0);
> }
>
> +static int mlx5e_stats_get_per_prio(struct mlx5_core_dev *mdev,
> + u32 *ppcnt_per_prio, int prio)
> +{
> + u32 in[MLX5_ST_SZ_DW(ppcnt_reg)] = {};
> + int sz = MLX5_ST_SZ_BYTES(ppcnt_reg);
> +
> + if (!(MLX5_CAP_PCAM_FEATURE(mdev, pfcc_mask) &&
> + MLX5_CAP_DEBUG(mdev, stall_detect)))
> + return -EOPNOTSUPP;
> +
> + MLX5_SET(ppcnt_reg, in, local_port, 1);
> + MLX5_SET(ppcnt_reg, in, grp, MLX5_PER_PRIORITY_COUNTERS_GROUP);
> + MLX5_SET(ppcnt_reg, in, prio_tc, prio);
> + return mlx5_core_access_reg(mdev, in, sz, ppcnt_per_prio, sz,
> + MLX5_REG_PPCNT, 0, 0);
> +}
> +
> void mlx5e_stats_pause_get(struct mlx5e_priv *priv,
> struct ethtool_pause_stats *pause_stats)
> {
> u32 ppcnt_ieee_802_3[MLX5_ST_SZ_DW(ppcnt_reg)];
> struct mlx5_core_dev *mdev = priv->mdev;
> + u64 ps_stats = 0;
> + int prio;
>
> if (mlx5e_stats_get_ieee(mdev, ppcnt_ieee_802_3))
> return;
> @@ -933,6 +952,17 @@ void mlx5e_stats_pause_get(struct mlx5e_priv *priv,
> MLX5E_READ_CTR64_BE_F(ppcnt_ieee_802_3,
> eth_802_3_cntrs_grp_data_layout,
> a_pause_mac_ctrl_frames_received);
> +
> + for (prio = 0; prio < NUM_PPORT_PRIO; prio++) {
> + if (mlx5e_stats_get_per_prio(mdev, ppcnt_ieee_802_3, prio))
> + return;
> +
> + ps_stats += MLX5E_READ_CTR64_BE_F(ppcnt_ieee_802_3,
> + eth_per_prio_grp_data_layout,
> + device_stall_critical_watermark_cnt);
> + }
> +
> + pause_stats->tx_pause_storm_events = ps_stats;
> }
>
> void mlx5e_stats_eth_phy_get(struct mlx5e_priv *priv,
It would be nice if someone at nVidia could have a look at the mlx bits
here. Waiting a little longer for that.
Thanks,
Paolo
next prev parent reply other threads:[~2026-03-05 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 23:01 [net-next V4 0/5] net: ethtool: Track TX pause storm Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 1/5] net: ethtool: Track pause storm events Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 2/5] net: ethtool: Update doc for tunable Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 3/5] eth: fbnic: Add protection against pause storm Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 4/5] eth: fbnic: Fetch TX pause storm stats Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 5/5] eth: mlx5: Move pause storm errors to pause stats Mohsin Bashir
2026-03-05 11:26 ` Paolo Abeni [this message]
2026-03-05 14:12 ` Tariq Toukan
2026-03-05 15:43 ` Mohsin Bashir
2026-03-05 15:40 ` [net-next V4 0/5] net: ethtool: Track TX pause storm 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=f9fef510-09bb-44b5-8340-c472f3b95deb@redhat.com \
--to=pabeni@redhat.com \
--cc=alexanderduyck@fb.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dg573847474@gmail.com \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mbloch@nvidia.com \
--cc=mike.marciniszyn@gmail.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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